DBCC CHECKDB and DBCC CHECKALLOC respectively checks integrity of SQL database objects and consistency of disk space allocation structures. But, sometimes they may show their limitations, when get failed to do a specific task. Here, we are going to discuss when these commands don’t report few allocation inconsistencies, such as the mentioned below:
8904 - Extent X in database ID Y is allocated by more than one allocation object.
8913 - Extent X is allocated to X and at least one other object.
As a resolution, Microsoft has suggested to obtain the latest service pack, which contains the newer code to judge the database inconsistencies and hence the errors.
Actually, as you go deeper into the problem, you may discover that 8904 and 8913 are the SQL errors, which get generated due to some hardware issues. Now, this is the critical situation and needs to be faced with SQL repair way.
As the first resort, you will definitely look into the most obvious SQL recovery technique i.e. using the DBCC CHECKDB and DBCC CHECKALLOC. But, its use has been recommended with REPAIR_ALLOW_DATA_LOSS option, which is a real issue for the database owner, if you get some other errors also on run of DBCC CHECKDB. Use of the specified command will make you compromise with the data as it deletes what it is unable to understand.
However, for the effective and safe MDF repair, use third party applications which better understand the concept. MDF recovery applications have the scanning mechanism to correct the SQL database corruption issues.
SQL repair techniques, applied by these utilities, are complete for each database object. Moreover, this is quite easy to implement them through the understandable steps. The best software makes SQL recovery more effectual, so look for the one.
So far, the best MDF repair has been judged through Stellar Phoenix SQL Database Recovery, which is a well-built application to scan, repair and restore the corrupted database. With its interactive interface and great scanning abilities, you would a find a superb MDF recovery done in an easy way. This supports SQL Server 2000 and 2005.
