Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=%ld; page# pointing to this page=%ld; previous page# indicated on this page=%ld)
This error occurs when SQL Server detects an inconsistency in the page linkage of one of the page chains associated with a table ¾ for example, when a page's next pointer points to a page whose previous pointer points back to a different page. There is one doubly-linked page chain for the table data as well as one for each index level.
Important This is a serious error and must be corrected immediately.
If DBCC statements detect this error during run-time processing, error 605 will also occur.
Determine which table is corrupt by examining the current page in the error message. For additional information about associating a page with an object, see "Associating a Page with an Object" in Chapter 24, "Additional Problem-solving Techniques." If the page is associated with an index, it is sometimes possible to resolve the problem by dropping the index. In most cases, you must recover the database from a known clean backup.
You should also examine your operating-system error log file, in addition to the SQL Server error log, to determine if hardware errors might have caused the corruption.
If the problem persists, contact your primary support provider. Have the output from the appropriate DBCC statements available for review.