Thursday 7 September 2017

SQL SERVER REPAIR DATABASE FROM SUSPECT MODE

SQL SERVER REPAIR DATABASE FROM SUSPECT MODE

SQL Server database go into suspect mode. During that moment, you cannot work on the database as database go into suspect mode because primary file group get damaged and database fails to recover during the start of SQL Server.


SQL Server Suspect Database Reasons


  • Log files or data files have got damaged
  • Due to lack of disk space, suspect mode like issues crops up in SQL Server database
  • Due to improper shutdown of database Server, you mostly find SQL database in suspect mode
  • Inability of SQL to complete rollback operation or roll forward operation
  • How to Repair SQL Server Suspect Database


Trouble Shooting Steps:

1. Change the status of your database.
2. Set the database in 'Emergency' mode such as:

Query: ALTER DATABASE <DatabaseName> SET EMERGENCY


3. Check for any of the inconsistency by using Query: DBCC checkdb('DatabaseName')
4. Bring the database to MULTI USER mode

 Query:-ALTER DATABASE [DatabseName] SET MULTI_USER

5. If any error message even after using DBCC CHECKDB command, then quickly bring the database in SINGLE USER MODE by running the query mentioned below:

Query :-ALTER DATABASE <DatabaseName> SET SINGLE_USER WITH ROLLBACK IMMEDIATE;