Comments
1 comment
-
Hello,
Thanks for the interesting post. We should probably do something in the script to compensate for this, but it seems to be an extremely rare potential problem. As I understand, this could more likely be caused by a maintenence plan or a DBCC REINDEX running on a table as another user manipulating data. This may be worth investigating on your end.
Add comment
Please sign in to leave a comment.
Could not continue scan with NOLOCK due to data movement.