SQL Server Performance, DBA Best Practices & Enterprise Data Solutions | MyTechMantra
FacebookXPinterestEmailGoogle+LinkedInWhatsApp
Home » SQL Server » How to Repair Database in Suspect Mode in SQL Server
DBADisaster RecoverySQL Server

How to Repair Database in Suspect Mode in SQL Server

Ashish Kumar Mehta
6 min read

Summary

There are times when you connect to an SQL Server Instance you will find the database being marked as SUSPECT. In such a scenario, you will not be able to connect to the database to read and write data. This article outlines the steps which you need to follow to recover your database which is marked SUSPECT.

Primary reasons when an SQL Server Database is marked in Suspect Mode

  • System Issues
  • Transaction Log File is Missing
  • SQL Server Crash
  • Database Files are inaccessible
  • SQL Server Database Operation Failures
  • Due to Improper shut down of SQL Server System
  • Due to Sudden Power Outage
  • Low Disk Space Issues
  • Hardware Failure


The steps mentioned in this article works on SQL Server 2005 and all higher versions.

Steps to Fix the SQL Server Database Suspect Mode Error

Step 1: Bring Database Online in EMERGENCY MODE
Step 2: Perform Consistency Check Using DBCC Command DBCC CHECKDB
Step 3: Bring the Database in SINGLE_USER Mode to ROLLBACK TRANSACTION
Step 4: Take a Full Backup of the User Database which was marked Suspect Before
Step 5: Execute DBCC CHECKDB WITH REPAIR ALLOW DATA LOSS (Caution: It will result in Data Loss)
Step 6: Once the above command has executed successful. Bring the Database in MULTI_USER Mode for normal read and write operations

If you have database backups which allows you Point in Time Recovery then it is always recommended to restore your database from the available SQL Server Database Backups. However, do consider you have enough space available on the server to restore the database.



Become a Pro

Accelerate Your SQL Server Mastery. Advance your career by exploring our Expert-Level T-SQL, Developer & DBA Guides covering Advanced Performance Tuning, Index Optimization, Failover Clustering, T-SQL Optimization, and Professional Troubleshooting.

Steps by Step Guide to Repair Suspect Database in SQL Server are:

1. Execute the below mentioned TSQL code to identify all the databases which are marked as SUSPECT.

USE master
GO

SELECT NAME,STATE_DESC FROM SYS.DATABASES
WHERE STATE_DESC='SUSPECT'
GO

Due to a hardware failure one of our database namely BPO was marked SUSPECT when the SQL Server came back online. Already due to the hardware failure we had downtime for more than two hours and adding to that when the server came back online our mostly critical database was marked as SUSPECT.

2. Open the latest SQL Server Error Log and check for errors logged for the database which is marked as suspect. You can open SQL Server Error Log by expanding Management Node -> SQL Server Error Logs. In my server I could find below mentioned entries in SQL Server Error Logs.

Sample Error Messages within SQL Server Error Log when database is marked as SUSPECT

Starting up database 'BPO'.

Error: 9003, Severity: 20, State: 9.

The log scan number (189624:16:2) passed to log scan in database 'BPO' is not valid.

This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf).

If this error occurred during replication, re-create the publication.
Otherwise, restore from backup if the problem results in a failure during startup.

Error: 3414, Severity: 21, State: 1.

An error occurred during recovery, preventing the database 'BPO' (database ID 10) from restarting.

Diagnose the recovery errors and fix them, or restore from a known good backup.
If errors are not corrected or expected, contact Technical Support.

CHECKDB for database 'BPO' finished without errors on 2009-12-15 11:30:28.320 (local time).

This is an informational message only; no user action is required.

3. When a database is in SUSPECT mode you will not be able to get connected to the database. Hence you need to bring the database first in EMERGENCY mode to repair the database. Execute the below mentioned TSQL code to bring the database in EMERGENCY mode.

USE master
GO

ALTER DATABASE BPO SET EMERGENCY
GO

Once the database is in EMERGENCY mode you will be able to query the database.



4. Execute the DBCC CHECKDB command which will check the logical and physical integrity of all the objects within the specified database.

DBCC CHECKDB (BPO)
GO

DBCC CHECKDB will take time depending upon the size of the database. Its always recommended to run DBCC CHECKDB as part of your regular maintenance schedule for all the SQL Server Databases.

5. Next step will be to bring the user database in SINGLE_USER mode by executing the below mentioned TSQL code.

ALTER DATABASE BPO SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO

When you repair your database using REPAIR_ALLOW_DATA_LOSS option of DBCC CHECKDB command there can be some loss of data.

Once the database is successfully repaired using REPAIR_ALLOW_DATA_LOSS option of DBCC CHECKDB command then there is no way to go back to the previous state.


6. Once the database is in SINGLE_USER mode execute the below TSQL code to repair the database.

DBCC CHECKDB (BPO, REPAIR_ALLOW_DATA_LOSS)
GO

7. Finally, execute the below mentioned TSQL command to allow MULTI_USER access to the database.

ALTER DATABASE BPO SET MULTI_USER
GO

Conclusion

This articles mentions the steps a DBA need to follow to recover database which is marked SUSPECT. As mentioned above, executing DBCC CHECKDB… REPAIR_ALLOW_DATA_LOSS DBCC Command will result in Data Loss. Therefore, if you have database backups which will allow “Point In Time” and have enough space on the server then it is the recommended approach.

Become a Pro

Accelerate Your SQL Server Mastery. Advance your career by exploring our Expert-Level T-SQL, Developer & DBA Guides covering Advanced Performance Tuning, Index Optimization, Failover Clustering, T-SQL Optimization, and Professional Troubleshooting.

SQL Server Disaster Recovery Tips

Ashish Kumar Mehta

Ashish Kumar Mehta is a distinguished Database Architect, Manager, and Technical Author with over two decades of hands-on IT experience. A recognized expert in the SQL Server ecosystem, Ashish’s expertise spans the entire evolution of the platform—from SQL Server 2000 to the cutting-edge SQL Server 2025.

Throughout his career, Ashish has authored 500+ technical articles across leading technology portals, establishing himself as a global voice in Database Administration (DBA), performance tuning, and cloud-native database modernization. His deep technical mastery extends beyond on-premises environments into the cloud, with a specialized focus on Google Cloud (GCP), AWS, and PostgreSQL.

As a consultant and project lead, he has architected and delivered high-stakes database infrastructure, data warehousing, and global migration projects for industry giants, including Microsoft, Hewlett-Packard (HP), Cognizant, and Centrica PLC (UK) / British Gas.

Ashish holds a degree in Computer Science Engineering and maintains an elite tier of industry certifications, including MCITP (Database Administrator), MCDBA (SQL Server 2000), and MCTS. His unique "Mantra" approach to technical training and documentation continues to help thousands of DBAs worldwide navigate the complexities of modern database management.

View all posts

You may also like

Follow us

Don't be shy, get in touch. We love meeting interesting people and making new friends.