subject: Resolution: Dbcc Checkdb Cannot Handle Severe Database Corruption [print this page] Microsoft SQL Server is a robust database management system, which offers a powerful database that ensures absolute data safety. MS SQL Server has an inbuilt SQL recovery utility, called DBCC CHECKDB, to fix minor issues with the database. The tool has a number of parameters to handle different kinds of problems. However, DBCC CHECKDB cannot necessarily handle all corruption problems, particularly the severe ones. In such situations, you need to use third-party SQL database recovery tools to get your data recovered.
DBCC CHECKDB command thoroughly checks the physical and logical integrity of SQL Server Database or Master Database File (MDF file). When it detects any kind of corruption, then it attempts to fix it at the maximum level of possibility. But, if it cannot repair the database, it shows you an error indicating the failure of the tool. The tool also shows the extent of the problem, so that you can identify the actual cause of this problem. For example, you may get the below error while checking the database integrity using DBCC CHECKDB command-
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886000) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886112) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
...
In order to sort out this problem, you need to identify the actual cause of the issue and fix it using SQL recovery solutions.
Grounds of the problem:
You get this error message when DBCC CHECKDB cannot handle the database corruption because the severity of damage is very high.
Resolution:
Try out any of the below MS SQL recovery methods to handle database corruption when the inbuilt utility fails-
Restore data from the most recent backup of SQL Server database. This is the best mthod to recover MDF database. However, the solution is useful only if you have an updated and valid backup.
In the else case, third-party MDF file recovery software becomes need of hour.
Such tools are particularly designed to perform SQL recovery in all corruption scenarios. They use highly-advanced scanning algorithms to ensure absolute recovery.
Stellar Phoenix SQL Recovery is the best software to recover SQL database from Microsoft SQL Server 2008, 2005, 2000, and 7.0.
