Automate Data Purity Investigation
-
Comments posted to this topic are about the item Automate Data Purity Investigation
-
Richard,
Thanks for the script - interesting technique.
It looks like line 175 was truncated (@Object needs to be @ObjectId).
Also, on first-run, I'm getting a message:
Warning: The maximum length of the row exceeds the permissible limit of 8060 bytes. For some combination of large values, the insert/update operation will fail.
.
I'll need to deconstruct the goings-on to find out why this is coming up (and it's just a warning, so maybe it's not a problem).
Cheers. Thanks for the post.
Mark
Just a cog in the wheel. -
Hi Mark,
Thanks for pointing out the warning. That is expected and I should have mentioned it in the article. It doesn't prevent the script from working.
Regarding the truncated line 175 I'm not at my desk at the moment, but I'll check it as soon as I get the chance. I tested it before uploading so not sure how that has happened.
-
OK, so the last 3 characters of line 175 have been truncated somehow.
This should be replaced with:
JOIN sys.columns c ON c.object_id = @ObjectIdDoes anyone know if it is possible to edit the scripts on SQL Server Central?
-
I've just found out that I can edit the script, so I have corrected the error and re-submitted.
-
Thanks for the script.
-
Oh, and thanks for the correction.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply