Logical inconsistencies caused 8928, 8939 and 8965 errors

Logical inconsistencies in the MS SQL database are mainly caused by corruption in your MDF file. These inconsistencies can be reported due to the unexpected behavior of your database. Few cases that help you assess if your MDF file is damaged are unexpected error messages, database impossibility and missing / inaccessible table records. An easy way to fix such inconsistency is to restore the database from an online backup. However, this solution may fail if the database administrator forgets to make a full backup or cannot open / find the backup file. In such cases of backup errors / inaccessibility, the DBCC CHECKDB command helps restore the database. This command, while successful, will fail in most cases when the database is severely damaged. In such situations, a third party SQL Recovery tool will help you recover your damaged MDF file and recover all your valuable database records.

Consider a practical scenario in which you will encounter a logical inconsistency error. To fix that error, when you run the DBCC CHECKDB command with the ALL_ ERRORMSGS parameter, you will see a list of below error messages:

Msg 8928, Level 16, State 1, Line 1

Object ID 1326627769, Index ID 1, Partition ID 72057594048872448, Mapping Unit ID Msg 8939, Level 16, State 98, Line 1

Table Error: Object ID 1326627769, Index ID 1, Partition ID 72057594048872448, Assign Unit ID …

Msg 8965, Level 16, State 1, Line 1

Table Error: Object ID 1326627769, Index ID 1, Partition ID 72057594048872448, Assign Unit ID

Msg 8929, Level 16, State 1, Line 1

Object ID 1326627769, index ID 1, partition ID 72057594048872448, alloc-unit ID 72057594055622656 (In-row data type): errors found in non-row data with ID 89622642688 data record ownership identified by RID = (1 : 77754: 1)

CHECKDB found 0 assignment errors and 4 consistency errors in table ‘[Table_Name](object ID 1326627769).

CHECKDB found 0 allocation errors and 4 consistency errors in database ‘[DB_Name]”.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB ([DB_Name]). “

Cause:

Damaged MDF files.

Resolution:

Go for a third-party SQL recovery tool.

Information about MS SQL Database Recovery Software:

An MS SQL Recovery tool is the safest way to recover a logically damaged database. Such SQL Database Recovery applications are easy to understand and do not require any technical expertise. The SQL Recovery tools also include an option to preview the repaired MDF file before saving it to the desired location.

Requested:

• MS SQL Server 2008

• MS SQL Server 2005

• MS SQL Server 2000



Source by Gaurav Kr