This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 470851 (SHILOH_BUGS)
Microsoft SQL Server 2000 fixes are distributed as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
When you run an UPDATE statement, and the connection's isolation level is set to READ UNCOMMITTED, you may receive the following error message:
Error: 644, Severity: 21, State: 6 Could not find the index entry for RID '%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
This problem only occurs when an index scan is used as part of the update operation, and the index scan is performed as a parallel operation. When the isolation level is set to READ UNCOMMITTED, locks are not held on rows that qualify for the scan from the time of the scan to the actual update. This behavior could permit other connections to modify a row that has already qualified for the update before the update operation is complete. In this situation, you can safely ignore the 644 error message. The UPDATE statement correctly reports that a specific row cannot be found and was terminated, and any changes that may have been made are rolled back. This hotfix makes sure that the locks are held on qualifying rows from the time of the scan to the update. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Microsoft SQL Server 2000 Developer Edition, Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2000 Enterprise Edition, Microsoft SQL Server 2000 Personal Edition, Microsoft SQL Server 2000, Workgroup Edition, Microsoft SQL Server 2000 Desktop Engine (Windows), Microsoft SQL Server 2000 Enterprise Edition 64-bit