When you try to update table rows or insert table rows into a table in Microsoft SQL Server 2000, you may receive an error message that resembles one of the following in the SQL Server 2000 Errorlog file:
Error message 1
Error: 644, Severity: 21, State: 5
Could not find the index entry for RID 'Number' in index page (IndexPage), index ID IndexID, database 'TestDB'.
Error message 2
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID Number, Index ID IndexID. Keys out of order on page (IndexPage), slots 184 and 185.
If you update table rows, you may experience this problem because an update operation is a delete operation followed by an insert operation.
When this problem occurs, the SQL data in the table rows is not lost. Instead, the table rows are inserted into the table in an incorrect order according to the index key.
This problem occurs if the following conditions are true:
When SQL Server inserts the table rows, one of the original pages that contain the table is split into two pages to create sufficient space to insert the table rows.
All the table rows are sorted according to an index key.
The following behavior occurs:
SQL Server tries to insert the table rows in the top half of the original page that will be split.
The insert operation causes the table rows in the bottom half of the original page to move to the new page.
The index key that is used to sort the table rows causes the new page to have a sort order that comes before the original page.
Note This behavior is known as a left page split.
Before the original page is split into two pages, the original page contains ghost records.
The Ghost Record Cleanup thread removes the ghost records from the original page after the original page is split into two pages. However, the thread removes these records before the table rows in the bottom half of the original page are moved to the new page.
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.
Note This issue does not occur on systems that use the Intel Itanium processor architecture.
The system is running a 64-bit version of the Microsoft Windows Server operating system.
The system is running a 32-bit version of SQL Server 2000.
We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
How to obtain the latest SQL Server 2000 service pack
You do not have to restart the computer after you apply this hotfix.
You do not have to change the registry.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
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 item in Control Panel.
To confirm that you experience this problem, you must provide the following information to Microsoft Customer Support Services:
Determine the page number or page numbers from the error messages that are mentioned in the "Symptoms" section. Page numbers are available in the SQL Server Errorlog files and in the Windows Application event log.
Obtain a copy of a transaction log backup file that covers the time during which the page was first used. Typically, this transaction log backup file is the next transaction log backup file that was created after you first receive the error messages that are mentioned in the "Symptoms" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base: