FIX: SP2 Regression: Update That Contains a Join Causes a 601 Error Message and Produces Incorrect Results

Article translations Article translations
Article ID: 275427 - View products that this article applies to.
This article was previously published under Q275427
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 58168 (SQLBUG_70)
Expand all | Collapse all


When SQL Server is run on a multiple processor computer it is possible for an UPDATE statement that contains a JOIN to cause the following 601 error message to occur:
"Could not continue scan with NOLOCK due to data movement."
The number of rows affected by the operation will be incorrect.

On a single processor computer, the query reports that the UPDATE completed successfully instead of reporting the number of rows affected if there are no indexes on any of the tables involved in the UPDATE statement. With indexes for the tables involved in the join but no index on the updated table, the number of rows affected might be reported but the number is incorrect.


To work around this problem, add an index to the table that is being updated. The index does not need to be unique or clustered.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 275427 - Last Review: October 21, 2013 - Revision: 2.1
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix kbqfe KB275427

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from