Steps to Repair SQL Server MDF File When DBCC CHECKDB Fails

Today, we will talk about DBCC CHECKDB command of MS SQL Server database. This is basically repair command used by MS SQL Server to check the physical and logical integrity of all the objects present in the selected database. Thus, if you have run DBCC CHECKDB command on your SQL database then you do not require running DBCC CHECKALLOC, DBCC CHECKCATALOG, and DBCC CHECKTABLE commands individually as DBCC CHECKDB integrates all these commands. Though DBCC CHECKDB is one of the best repair commands to deal with the corruption of SQL database but at times this command too fails to fix the issue and returns some errors. One solution to deal this situation is to restore database from backup. However, if you do not have the backup of your database or the backup too gets corrupt then you need to opt for SQL database recoverythrough reliable third-party database recovery software.

Let us exemplify the above situation. Suppose, you try to mount your SQL database and see the consistency issues which are occurring in the database. Thus, to resolve this issue when you run DBCC CHECKDB command, you encounter the following error message:

Server: Msg 8929, Level 16, State 1, Line 1
Object ID 1979154096: Errors found in text ID 379493089280 owned by data record identified by RID = (1:647611:14) PK1 = 1300583.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 1979154096: Errors found in text ID 379544338432 owned by data record identified by RID = (1:648136:32) PK1 = 1300903.

Table error: Object ID 1979154096, index ID 255, page (1:558593). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 0, text ID 552407334912 is referenced by page (1:1387313), slot 46, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1

CHECKDB found 0 allocation errors and 33 consistency errors in table ‘QTI_RESULT_DATA’ (object ID 1979154096).
CHECKDB found 0 allocation errors and 33 consistency errors in database ‘bb_bb60′.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (bb_bb60 ).”

Thus, soon after the display of this message, the entire database records of your database become inaccessible. The primary cause of the occurrence of this error is severe damage or corruption in MS SQL database. Some measures to solve this problem are:

  • First of all check for the physical damage to any of the components of your system. To do so check application, system, and SQL Server logs. Thus, identify the physically damaged component in the log and change it with a new component.
  • If there is no physical damage in the system then run DBCC CHECKDB command with repair_allow_data_loss parameter. This is one of those commands which resolve the problems of SQL database corruption for sure but there are chances of losing some critical data saved on your database after running it. At this situation to not to lose your precious data saved on your database opt effective third-party SQL recovery software.

SQL Recoveryis one of the robust and efficient SQL repair tool which repairs and restores the components of corrupt SQL database created in MS SQL Server 7.0, 2000, 2005, 2008, 2008 R2 and 2012. The software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

If you want to skip all this process and perform such task easy, accurately and fast then go for a third party application. This application surely help you. You can use this application at free of cost to repair sql database and also eligible to see preview of recover data but you are not allow to save recover data, For saving this data you need to register the full version license. You can download this application from here:  

Advertisements
Tagged , , , , , , , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: