Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 CHECKDB consistency errors
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

1 Posts

Posted - 01/11/2013 :  11:21:31  Show Profile  Reply with Quote
I'm not a DBA but a remote developer restoring a customer's database for the first time. I received a .bak file and forced it to restore with CONTINUE_AFTER_ERROR which reported damage. Then ran DBCC CHECKDB and these are the relevant messages returned:

DBCC results for 'TagHist'.
Msg 8928, Level 16, State 1, Line 1
Object ID 549576996, index ID 0, partition ID 36017078009856, alloc unit ID 36017078009856 (type In-row data): Page (1:953823) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 549576996, index ID 0, partition ID 36017078009856, alloc unit ID 36017078009856 (type In-row data), page (1:953823). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -1.
There are 10127360 rows in 141414 pages for object "TagHist".
CHECKDB found 0 allocation errors and 2 consistency errors in table 'TagHist' (object ID 549576996).
CHECKDB found 0 allocation errors and 2 consistency errors in database 'ASIS'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (ASIS).

What do these consistency errors mean? Does it mean the customer has a bad disk and the only way to fix it is for them to replace the disk, recover/fix the data and then send me a new .bak file? Or is the problem with my disk or something else?

Jeff Moden
Aged Yak Warrior

652 Posts

Posted - 01/12/2013 :  11:55:44  Show Profile  Reply with Quote
There are a thousand different reasons for such errors. It can be anything from a sector that went bad on their disk to (normally not) a whacky lights out situation that hammered the server.

Tell the customer they have a problem and that they should try a test restore on their end to confirm.

--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for "Row By Agonizing Row".

First step towards the paradigm shift of writing Set Based code:
"Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

When writing schedules, keep the following in mind:
"If you want it real bad, that's the way you'll likely get it."
Go to Top of Page

Starting Member

11 Posts

Posted - 01/16/2013 :  02:46:31  Show Profile  Reply with Quote
RecoveryFix for SQL database is a smart tool that quickly recovers corrupt MDF files. It recovers all database objects like views, indexes, triggers, stored procedures, user defined functions and others from inaccessible MDF file. The software thoroughly scans the local disk or network drive to find corrupt SQL databases. It allows the user to rebuild offline MDF files in a batch. Demo version of the software generates a preview of all recovered database objects on computer screen. You can restore the database modules either on Live SQL Server or offline disk with full version of the software.


Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000