{"id":805724,"date":"2020-06-24T13:52:48","date_gmt":"2020-06-24T13:52:48","guid":{"rendered":"https:\/\/www.knowband.com\/blog\/?p=805724\/"},"modified":"2024-06-05T05:53:33","modified_gmt":"2024-06-05T05:53:33","slug":"how-to-repair-a-suspect-database-in-mssql","status":"publish","type":"post","link":"https:\/\/www.knowband.com\/blog\/tips\/how-to-repair-a-suspect-database-in-mssql\/","title":{"rendered":"How To Repair A Suspect Database In MSSQL"},"content":{"rendered":"

The database may occasionally be marked as SUSPECT when you connect to a SQL Server instance. You won’t be able to connect to the database to read and write data in this situation. The procedures you must follow to restore your database that has been marked as SUSPECT are discussed in the article.<\/p>\n

Reasons of this error<\/h2>\n

Here are some following causes due to we have to face the suspected database error.<\/p>\n

    \n
  1. Restart or shut down the Database without shutting down the SharePoint server.<\/li>\n
  2. The database could have become corrupted.<\/li>\n
  3. There is not enough space available for the SQL Server to recover the database during startup.<\/li>\n
  4. The database cannot be opened due to inaccessible files or insufficient memory or disk space.<\/li>\n
  5. The database files are being held by the operating systems, third-party backup software etc.<\/li>\n
  6. There was an unexpected SQL Server Shutdown, power failure, or hardware failure.<\/li>\n<\/ol>\n

    Resolutions<\/h2>\n

    Here are a few steps to resolve this issue. First, make sure you have Microsoft SQL Server Management Studio in your system.<\/p>\n

    1.\u00a0\u00a0 First, open your Microsoft SQL Server Management Studio and fill in your database credentials to connect to your database.<\/strong><\/p>\n

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

    2.\u00a0\u00a0 Then right-click on your suspected DB and click on the New Query button to write a query.<\/strong><\/p>\n

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

    3.\u00a0\u00a0After that run the below commands one by one Here you need to replace [YourDatabase] with the name of your database Name.<\/strong><\/p>\n

    a. Reset the database status to clear any error flags.<\/span><\/p>\n\n\n\n
    EXEC sp_resetstatus [YourDatabase];<\/b><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    This command resets the status of the specified database. If a database is marked as “suspect” or in a similar state, this command can clear that status. It’s the first step to attempt to bring the database back online.<\/span><\/p>\n

    b. Put the database into a state where it can be safely checked and repaired (emergency mode).<\/p>\n\n\n\n
    ALTER DATABASE [YourDatabase] SET EMERGENCY<\/b><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    This command sets the database to emergency mode. Emergency mode is a special state used for troubleshooting. In this mode:<\/span><\/p>\n