Article ID: 242953 - Last Review: November 30, 2007 - Revision: 3.3

SMS: "Table Corrupt" When Running DBCC Checkcatalog Against SMS Database

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q242953

Expand all | Collapse all

SYMPTOMS

Database consistency checks (DBCCs) may produce error messages when they are run against a Systems Management Server (SMS) 2.0 SP1 SQL 7.0 database, even though the database is working correctly. For example, when you run DBCC "checkcatalog" against an SMS SQL 7.0 database, an error message similar to the following message may be generated:

Server: Msg 2513, Level 16, State 15, Line 1
Table Corrupt: Object ID 322100188 (object 'Summarizer_ComponentTallys') does not match between 'SYSREFERENCES' and 'SYSCOLUMNS.'.
DBCC results for 'current database'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

However, using the database indicates that the database is not corrupted, and all other DBCC checks, including DBCC "checkdb" run without any error messages.

Back to the top

WORKAROUND

You can ignore this error message. The SYSREFERENCES and SYSCOLUMNS tables are created by SQL in each database. These tables are not used by SMS.

Back to the top

STATUS

This problem is resolved in SQL 7.0 Service Pack 2 and later.

Back to the top

MORE INFORMATION

From SQL books online:

sysreferences (T-SQL)
Contains mappings of FOREIGN KEY constraint definitions to the referenced columns. This table is stored in each database.

syscolumns (T-SQL)
Contains one row for every column in every table and view, and a row for each parameter in a stored procedure. This table is in each database.

Back to the top