February 5, 2002 at 9:32 am
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not continue scan with NOLOCK due to data movement.
We are using SQL server 7.0 with Service pack 3. This is one error that we get quite often. According to Microsoft this problem should have been fixed in SP3. Any other suggestions or things I can try to fix this problem
February 5, 2002 at 11:31 am
Sorry, haven't seen it.
Do you really need the NOLOCK? Are there that many locks being held?
Steve Jones
February 5, 2002 at 11:57 am
Yes, we have few tables where user can add or update the records. If during the reads from those tables we don't put NoLocks the queries take very very long time because of all the exclusive locks due to updates.
And moreover we don't get this error message each and everytime I run those Stored procedures. Only say 1% of the times I run these stored procedures.
quote:
Sorry, haven't seen it.Do you really need the NOLOCK? Are there that many locks being held?
Steve Jones
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply