

The command sets the database in ‘ single user mode’. ALTER DATABASE DB_Name SET SINGLE_USER WITH ROLLBACK IMMEDIATE The above command helps check the integrity of all database objects. Note: Members of the sysadmin fixed server can only access this right. In this mode, users only get read-only permission to access the database. This command puts the database in EMERGENCY mode. For detailed information, refer to this link. Note: You can also use the ‘sp_resetstatus’ stored procedure to turn off the suspect flag on a database. Open a new query window in SSMS, and then run the following commands:

If none of the above tricks help resolve the error, perform these steps: Step 1: Use EMERGENCY Mode to Repair a Suspect Database

Restart the SQL Server Management Studio (SSMS).Disconnect and reconnect the SQL connection.But, before attempting this solution, try the following tricks to fix Microsoft SQL Server 2008 R2 Error 926 MSDB: Doing so will help you restore access to the database marked as suspect. If you don’t have recent backup or the backup is corrupt, set the database in EMERGENCY mode and try the DBCC CHECKDB repair operations. In that case, try restoring the database from the last known database backup. If this doesn’t work, there must be some form of database corruption. If the recovery failed due to an I/O error (a torn page) or any other hardware issue, try resolving the hardware issue first to fix the error. Using the RESTORE database or RESTORE LOG commandsĬheck the SQL Server error log to identify what caused the error.Following are some operations that result in SQL error 926: So, you will need to repair or recover MS SQL database from suspect mode to make it accessible again. The above error message indicates that ‘database is marked as suspect due to failed recovery process’, which prevents the database from opening. Figure 1 – Microsoft SQL Server, Error: 926 Message
