| DBCC CHECKDB is a command that is mainly used to | | | | The repair level on the DBCC statement caused this |
| check the logical and physical integrity of MS SQL | | | | repair to be bypassed. |
| database. The command can be executed with three | | | | The repair level on the DBCC statement caused this |
| different parameters repair_allow_data loss, | | | | repair to be bypassed. |
| repair_fast, and repair_rebuild to repair an MS SQL | | | | There are 1953 rows in 127 pages for object |
| database. While the command ensures absolute repair | | | | 'sysindexes'. |
| of logically damaged MS SQL database in most | | | | CHECKDB found 0 allocation errors and 6 consistency |
| cases, there might be certain situations when this | | | | errors in table 'sysindexes' (object ID 2). |
| command fails to perform complete repair. Such | | | | DBCC results for 'syscolumns'. |
| situations occur when the corruption level of database | | | | There are 10093 rows in 218 pages for object |
| is too high and beyond the limits of the command. | | | | 'syscolumns'. |
| However, a valid backup acts as a boon in such | | | | DBCC results for 'systypes'. |
| scenarios and allows the user to access the database. | | | | There are 32 rows in 1 pages for object 'systypes'. |
| But if in case the user has not maintained any | | | | DBCC results for 'syscomments'. " |
| database backup, then the only way to repair the | | | | The database remains in the corrupted state since the |
| database is by using an effective third-party MDF | | | | DBCC CHECKDB command is unable to repair the |
| Repair software. | | | | database. |
| To elaborate the above scenario, consider a practical | | | | Cause: |
| case where your MS SQL database gets corrupted | | | | The database is severely corrupted and might require |
| due to metadata structure damage. Now, when you | | | | rebuilding of indexes or de-allocating of all the corrupt |
| execute the DBCC CHECKDB command (with | | | | pages. |
| repair_fast parameter) to repair your database, you | | | | Resolution: |
| encounter the below error message: | | | | To overcome corruption of your database, the user |
| "DBCC results for 'sysindexes'. | | | | needs to repair the database by running DBCC |
| The repair level on the DBCC statement caused this | | | | CHECKDB command with repair_allow_data loss |
| repair to be bypassed. | | | | parameter. While doing so might resolve the error |
| The system cannot self repair this error. | | | | message, it will also result into deletion of data from |
| The repair level on the DBCC statement caused this | | | | your database. To avoid any loss of data, you should |
| repair to be bypassed. | | | | opt for a commercial MDF File Repair application. Such |
| The repair level on the DBCC statement caused this | | | | MDF Repair tools do not overwrite or modify the |
| repair to be bypassed. | | | | original database during the repair process. |