Re: DBCC CHECKDB results - repairable?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 19:12:22 +0200

Below is a good place to start. And remember that the updated books online has *detailed and
specific* recommendations for all corruption types of errors.

http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John McLusky" <jmclusky@community.nospam> wrote in message 
news:efrPEYkpEHA.3520@TK2MSFTNGP11.phx.gbl...
>
> 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: 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 Errors
    ... Here's a start if you have corruption of a suspect database: ... "Prasad Koukuntla" wrote in message ... I got the following errors when I ran the DBCC Checkdb on my ... However, I am already running SQL SERVER SP3, ...
    (microsoft.public.sqlserver.server)
  • Re: Attempt to fetch logical page
    ... You have a corruption in your database. ... Second, if you are on SQL Server 2000, check the specific recommendations for your error. ... This error occurs when Microsoft® SQL ServerT detects database corruption. ... execute DBCC CHECKDB to determine the extent of the damage. ...
    (microsoft.public.sqlserver.server)
  • Re: DBCC CHECKDB WITH DATA_PURITY on production
    ... You need to run the dbcc checkdb with data purity only if the database ... If the database is created on SQL ... For databases created in SQL Server 2005 and later, column-value integrity ...
    (microsoft.public.sqlserver.server)