Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Collapse the table of content
Expand the table of content
Expand Minimize

Error 8971

SQL Server 2000

Error 8971

  Topic last updated -- January 2004

Severity Level 16
Message Text

Forwarded row mismatch: Object ID O_ID, page P_ID1, slot S_ID1 points to forwarded row page P_ID2, slot S_ID2; the forwarded row points back to page P_ID3, slot S_ID3.


In a heap, the forwarded row (S_ID2 on page P_ID2) must point back to the forwarding row (S_ID1 on page P_ID1). This message means that the forwarded row points back to the wrong row.



Run hardware diagnostics and correct any problems. Also examine the Microsoft® Windows NT® system and application logs and the SQL Server™ error log to see if the error occurred as the result of hardware failure. Fix any hardware related problems.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to ensure that your system does not have write caching enabled on the disk controller. If you suspect this to be the problem, contact your hardware vendor.

Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.


If the problem is not hardware related and a known clean backup is available, restore the database from the backup. 


If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

Caution  If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

Performing a repair will fix the back-pointer in row S_ID2 on page P_ID2 to point back to row S_ID1 on page P_ID1, and then will rebuild any non-clustered indexes.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

See Also


Errors 8000 - 8999

Reporting Errors to Your Primary Support Provider

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft