| Microsoft SQL Server includes an inbuilt utility, called | | | | inaccessible. To gain access of your valuable data, |
| DBCC CHECKDB, to check the consistency and | | | | SQL database recovery is required. |
| integrity of MDF (Master Database File). However, | | | | Root of the problem: |
| sometimes the DBCC CHECKDB process does not | | | | DBCC CHECKDB utility checks the logical and physical |
| complete successfully and can not fix the associated | | | | consistency of SQL Server database pages, allocation |
| issues. Database inconsistency can make the SQL | | | | pages, rows, system table referential integrity, index |
| Server database inaccessible and lead to severe data | | | | relationships, and other database structure checks. In |
| loss situations. In such cases, you need to recover | | | | case any one of these checks does not complete |
| SQL database, in order to extract data from it. | | | | successfully (depending upon the options that you |
| When you execute DBCC CHECKDB on an SQL | | | | have selected), errors are reported as part of this |
| database, an error message similar to the following | | | | command. |
| one, appears in ERRORLOG of Microsoft SQL | | | | This behavior may occur due to numerous reasons of |
| Server- | | | | database corruption, such as hardware system |
| "2010-03-31 22:07:06.34 spid53 DBCC CHECKDB | | | | problems, file system corruption, damaged pages in |
| (mydb) executed by MYDOMAIN\theuser found 15 | | | | memory, or issues with MS SQL Server Engine. |
| errors and repaired 0 errors. Elapsed time: 0 hours 0 | | | | Resolution: |
| minutes 0 seconds. Internal database snapshot has | | | | The most excellent solution to fix DBCC CHECKDB |
| split point LSN = 00000026:0000089d:0001 and first | | | | consistency errors is to restore the database from the |
| LSN = 00000026:0000089c:0001. This is an | | | | most recent backup. However, if backup is not |
| informational message only. No user action is required." | | | | available or updated, CHECKDB offers an option to |
| The above message shows the total number of | | | | repair the errors. |
| database consistency errors in SQL database and | | | | When all else fails, SQL recovery software are |
| how many of them are repaired. The message | | | | required to repair and restore the damaged SQL |
| information, start from 'internal database snapshot...', | | | | Server database. They employs high-end scanning |
| appears only if you run the DBCC CHECKDB online. | | | | techniques to thoroughly scan entire database and |
| The database consistency check process is halted | | | | extract all of its inaccessible objects. The MS SQL |
| with this error message and your database remains | | | | repair tools are pretty safe and easy to use. |