{"id":11553,"date":"2021-04-22T15:38:36","date_gmt":"2021-04-22T10:08:36","guid":{"rendered":"https:\/\/www.stellarinfo.co.in\/blog\/?p=11553"},"modified":"2025-10-10T11:28:37","modified_gmt":"2025-10-10T05:58:37","slug":"how-to-repair-database-dbcc-checkdb-doesnt-work","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.co.in\/blog\/how-to-repair-database-dbcc-checkdb-doesnt-work\/","title":{"rendered":"How to Repair Database if DBCC CHECKDB doesn’t Work?"},"content":{"rendered":"\n\n\n
Summary:<\/strong> When your SQL database encounters consistency errors or gets corrupt, you can use the DBCC CHECKDB command and get to know the details of the issue(s) with the database. DBCC CHECKDB command<\/strong> checks the SQL database for physical and logical consistency<\/strong> issues. It checks the consistency of database pages, rows, allocation pages, index relationships, system table referential integrity, etc. This guide details the process of utilizing the DBCC CHECKDB command to rectify errors in the SQL database. Additionally, we will explore an advanced MS SQL repair software as an alternative solution when the standard DBCC CHECKDB proves ineffective in repairing the database.<\/span><\/span><\/p>\n

\"Stellar<\/a><\/p>\n

 <\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n

Given below is the syntax of the command:<\/em><\/p>\n

DBCC CHECKDB (Affected_DB) WITH NO_INFOMSGS, ALL_ERRORMSGS<\/strong><\/p>\n

This command tells you about the minimum level of repair you need to apply to fix the database.<\/p>\n

For example, the output of the command could be something similar to the one given below:<\/p>\n

CHECKDB found 0 allocation errors and 10 consistency errors in database Affected_DB’.\u00a0Repair_allow_data_loss<\/strong>\u00a0is the minimum repair level for the errors found by DBCC CHECKDB (Affected_DB)<\/strong><\/em><\/p>\n

\"\"<\/a><\/p>\n

Repairing Database by Using DBCC CHECKDB Repair Levels<\/strong><\/h2>\n

SQL Server offers three repair levels — REPAIR_FAST, REPAIR_REBUILD,<\/strong> and REPAIR_ALLOW_DATA_LOSS.<\/strong> Based on the DBCC CHECKDB<\/strong> recommendation of the required repair level, you can execute the DBCC CHECKDB<\/strong> command for repairing the database.<\/p>\n

Syntax of DBCC CHECKDB<\/strong> with repair options is as follows:<\/p>\n\n\n\n
DBCC CHECKDB
\n[ ( database_name | database_id | 0
\n[ , NOINDEX
\n| , { REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD } ]
\n) ]
\n[ WITH
\n{
\n[ ALL_ERRORMSGS ]
\n[ , EXTENDED_LOGICAL_CHECKS ]
\n[ , NO_INFOMSGS ]
\n[ , TABLOCK ]
\n[ , ESTIMATEONLY ]
\n[ , { PHYSICAL_ONLY | DATA_PURITY } ]
\n[ , MAXDOP = number_of_processors ]
\n}
\n]
\n] <\/span><\/span><\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n

Why DBCC CHECKDB for Repairing May Not Have Worked?<\/strong><\/h3>\n

If DBCC CHECKDB didn\u2019t work, it means you have used the REPAIR_FAST repair option as it doesn\u2019t perform any repair actions. REPAIR_FAST<\/strong> option is meant only for providing backward compatibility while you try to repair the database with other repair options.<\/p>\n

You may also not be able to repair the database by using REPAIR_REBUILD<\/strong> if the database has errors involving FILESTREAM data. REPAIR_REBUILD performs repairs that have no possibility of data loss, such as repairing missing rows in non-clustered indexes, rebuilding an index, etc. It can\u2019t perform a repair action that in any way may result in data loss.<\/p>\n

Also read,\u00a0How to Restore Database in SQL Server?<\/a><\/p>\n

Tried REPAIR_ALLOW_DATA_LOSS Option?<\/strong><\/h3>\n

If the other options haven\u2019t helped you resolve the problem, you can try to repair the database by running DBCC CHECKDB with the REPAIR_ALLOW_DATA_LOSS option. When the command runs with this option, the server tries to repair all the database consistency errors<\/strong>. It can eliminate the data which might have caused the issue.<\/p>\n

Thus, running DBCC CHECKDB with the REPAIR_ALLOW_DATA_LOSS<\/strong> option is effective.<\/p>\n

[CAUTION]:<\/em><\/strong><\/p>\n