DBCC CHECKDB results - repairable?

From: John McLusky (jmclusky_at_community.nospam)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 18:01:49 +0100

Hello,

I ran DBCC CHECKDB on a database with some performance issues today and
received several errors. I restored from a backup (from last week, the
earliest one we had) as the database has not gone into production use yet.
The database however does contain a considerable amount of data as we had
done a data conversion from the customer's previous solution.

The errors on the backup are as follows (I have snipped out the information
messages)

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2015398299, index ID 0: Page (1:402237) could not be processed.
See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 2015398299, index ID 0, page (1:402237), row 39. Test
(ColumnOffsets <= (nextRec - pRec)) failed. Values are 37 and 35.

There are 481044 rows in 2208 pages for object 'ORDERS'.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'ORDERS'
(object ID 2015398299).

CHECKDB found 0 allocation errors and 2 consistency errors in database
'CUST11838'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (CUST11838 ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.

Are these errors likely to be permanently repairable by running CHECKDB with
repair_allow_data_loss, or should we really be starting our data migration
processes again (delaying our customer's 'go live' by possibly 3-4 days)?

Many thanks,
John.

Relevant Pages

  • Re: DBCC CHCECKTABLE faults go away after reboot?
    ... The database with corrupt sysindexes cannot be repaired and will need to be ... documented reasons not to run CHECKDB on a very busy system. ... Microsoft SQL Server Storage Engine ... > - one database with sysindexes table failing DBCC CHECKDB, ...
    (microsoft.public.sqlserver.server)
  • Re: Corrupt backup - "An internal consistency error occurred", code 42000
    ... Yesterday, DBCC CHECKDB reported no errors on the 'base, though, and then I ... I was able to successfully mount the database by manually attaching the mdf ... showed no errors), and did a backup. ... I would expect that DTS operations would ...
    (microsoft.public.sqlserver.server)
  • Re: Database recovery with data file only
    ... Although DBCC CHECKDB can detect physical corruption, ... > up the database ken can execute a DBCC CHECKDB and confirm that database ... >> A preferable method is to restore from backup. ...
    (microsoft.public.sqlserver.server)
  • Re: DBCC CHECKDB results - repairable?
    ... > I ran DBCC CHECKDB on a database with some performance issues today and received several errors. ... > I restored from a backup as the database has not gone ... > repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB ...
    (microsoft.public.sqlserver.server)
  • Re: dbcc checkdb in Yukon
    ... Checkdb in Yukon uses ... database snapshots to allow online checks. ... >>> When dbcc checkdb or checkcatalog executed on master db of Yukon got ...
    (microsoft.public.sqlserver.server)