subject: DBCC CHECKTABLE Displays 8966 and 8944 Error Messages by:Mark Willium [print this page] Records stored in a MS SQL Server table become inaccessible when it gets corrupted due to record header corruption, metadata structure damage, application malfunction, and concurrent modification. To surmount table corruption, MS SQL Server provides an inbuilt table repair command known as 'DBCC CHECKTABLE'. The command checks the logical and physical integrity of the corrupted table and the indexed view. While in most cases, the command is successful in repairing corrupted tables, there are a few instances where the command falls short in repairing the MS SQL Server table. In such situations, the command displays an error message, exhibiting the exact reason for its failure. The table remains corrupt after DBCC CHECKTABLE failure message. To overcome such table corruption, an ideal option is to restore the table from an updated backup. However, in the absence of or in case of deficient table backup, the user needs to use a powerful third-party MDF Repair utility.
To explain the above scenario in detail, consider a practical case where you encounter the below error message while attempting to repair your corrupt table using DBCC CHECKTABLE command:
"Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:24) with latch type SH. sysindexes
failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 0, page (1:24), row 11. Test
Table error: Object ID 2, index ID 0, page (1:24), row 11. Test
(GetRecType (pRec) >= 0 && GetRecType (pRec) MDF Recovery tools use advanced repair solutions to repair the table and restore it at user-specified location.
About the author
I have completed my Ph.D in computer science and currently doing research on how to recover and repair corrupted database. During my research i found many third party software for several database recovery like sql recovery, sql repair, mdf recovery, mdf repair, db2 recovery, oracle recovery and many more. i am sharing my experience and knowledge with you all. For more details visit: http://www.mdfrecovery.com
