SQL Server fixes problem with system table error mismatch

Repair system tables (table Error-Object ID 2. Text, ntext, or image node (in page (1-875), slot 0, text ID 177078272) and the node is on the page (1-500), the reference at slot 14 does not match)

Repair database, should be a more familiar with the "strange" dongdong. The previous fix used a general fix statement, and today it was a stubborn mistake, NND,

The error message is as follows:

Server: Message 8929, Level 16, State 1, line 1

Object ID 2: An error was found in text ID 177078272, and the owner of the text is a data record identified by the RID = (1:627:1) ID = 1899153811 and indid = 10.

Server: Message 8961, Level 16, State 1, line 1

Table Error: Object ID 2. The text, ntext, or image node (located on the page (1:875), slot 0, text ID 177078272) is at the page (1:500) of the node and the reference at slot 14 does not match.

DBCC results for ' Yinyi '.

DBCC results for ' sysobjects '.

The object ' sysobjects ' has 419 rows, which are in 7 pages.

DBCC results for ' sysindexes '.

The object ' sysindexes ' has 451 rows, which are in 22 pages.

CHECKDB found 0 allocation errors and 2 consistency errors (in table ' sysindexes ', the table has an object ID of 2).

DBCC results for ' syscolumns '.

CHECKDB found 0 allocation errors and 2 consistency errors (in the database ' Yinyi ').

DBCC execution completed. If DBCC prints an error message, contact your system administrator.

This is a problem that has been repaired and still exists, because the hint is the system table sysobjects table has a problem, and has prompted the RID and ID, I will query out this data, to check the same type of database, also a field is not the same, and represents a number of affected rows, There is no corresponding difference. I was going to give up, but then I tried to clean up all the data of a table that was often used (truncate), and then checkdb no more errors. The data in this table is then queried and placed in a temporary table, then all the data is cleared, and then inserts from the temporary table are CHECKDB,

CHECKDB found 0 allocation errors and 0 consistency errors (in the database ' Yinyi ').

DBCC execution completed. If DBCC prints an error message, contact your system administrator.

Done, this phenomenon shows that in fact checkdb out if there are problems in the system table, our system will not be so easy to bad. The first thing you need to check is that you usually use the table, even if the checktable is not necessarily wrong, only according to your software in which a point will be wrong, analysis of the table, followed by the exclusion.

This article writes here that you want to encounter a similar table error: Object ID 2. Text, ntext, or image node (in page (1:875), slot 0, text ID 177078272) and the node in the page (1:500), slot 14, the reference does not match "the problem of friends are more careful, I hope to help!"