July 9, 2012 at 12:52 pm
Running DBCC Checkdb on a database yielded the following:
DBCC CHECKDB(N'MyDB') WITH NO_INFOMSGS
Table error: Object ID 2057110419, index ID 1, partition ID 72057597444161536, alloc unit ID 72057597501833216 (type In-row data). Page (1:7823149) is missing a reference from previous page (1:7823150). Possible chain linkage problem.
Table error: Object ID 2057110419, index ID 1, partition ID 72057597444161536, alloc unit ID 72057597501833216 (type In-row data). Page (1:7823150) was not seen in the scan although its parent (1:5720869) and previous (1:7823151) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'MyTable' (object ID 2057110419).
CHECKDB found 0 allocation errors and 2 consistency errors in database 'MyDB'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (MyDB).
(Names of DB and table changed...)
Index 1 is the clustered index on this table (and also it's PK), and there are no other indexes on this table. One of the columns in the PK (the last column) is an identity column. Client says that data appears to be only inserted into the table - and that they don't have a maintenance window. The table has ~ 200 million records.
I'm thinking that I should:
Restore the database to a parallel database, ensure that it is a clean DB with DBCC CHECKDB, and then check the gaps on the identity column.
Run the repair_rebuild on this database, and check for gaps on the identity column.
Compare the gaps, and we'll know which ones need replaced.
Gail, Paul, and other corruption gurus... do you see anything else that I should look into or have any other suggestions for how to handle this?
Thanks in advance for taking time out of your busy day to look / respond to this.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply