What you want to do if your database has gone into Suspect state, you will have to try bringing it online in order to perform analysis on the error cause. While you analyse the database, you do not want users to connect to the database. This can be done with a sequence of commands: USE MASTER; EXEC sp_resetstatus 'your_database_name'; ALTER DATABASE your_database_name SET EMERGENCY; When that's done, you will hopefully have your database in Emergency state rather than suspect. This means that the database is read-only, and only members of the sysadmin fixed server role can access the database. In this state, you can perform DBCC CHECKDB on the database, to analyse why it Went into suspect state in the first Place. From then, you'll have to do different things depending on what DBCC CHECKDB reports. But this is a start, to be able to analyse the database and decide on the next step(s).