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.
Reasons of this error
Here are some following causes due to we have to face the suspected database error.
- Restart or shut down the Database without shutting down the SharePoint server.
- The database could have become corrupted.
- There is not enough space available for the SQL Server to recover the database during startup.
- The database cannot be opened due to inaccessible files or insufficient memory or disk space.
- The database files are being held by the operating systems, third-party backup software etc.
- There was an unexpected SQL Server Shutdown, power failure, or hardware failure.
Resolutions
Here are a few steps to resolve this issue. First, make sure you have Microsoft SQL Server Management Studio in your system.
1. First, open your Microsoft SQL Server Management Studio and fill in your database credentials to connect to your database.
2. Then right-click on your suspected DB and click on the New Query button to write a query.
3. After that run the below commands one by one Here you need to replace [YourDatabase] with the name of your database Name.
a. Reset the database status to clear any error flags.
| EXEC sp_resetstatus [YourDatabase]; |
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.
b. Put the database into a state where it can be safely checked and repaired (emergency mode).
| ALTER DATABASE [YourDatabase] SET EMERGENCY |
This command sets the database to emergency mode. Emergency mode is a special state used for troubleshooting. In this mode:
- The database is set to read-only.
- Only members of the sysadmin role can access the database.
- It’s used when the database is severely damaged and cannot be accessed normally.
c. Check for any issues in the database.
| DBCC checkdb([YourDatabase]) |
This command runs the DBCC CHECKDB utility, which checks the physical and logical integrity of the entire database. It identifies any corruption or issues within the database.
d. Ensure no other users are connected to interfere with the repair process (single-user mode).
| ALTER DATABASE [YourDatabase] SET SINGLE_USER WITH ROLLBACK IMMEDIATE |
This command sets the database to single-user mode with immediate rollback. This means:
- Only one user can access the database at a time.
- Any other connections to the database are terminated immediately.
- It’s necessary to prevent other users from interfering with the repair process.
e. Repair the database, accepting that some data might be lost to fix the issues.
| DBCC CheckDB ([YourDatabase], REPAIR_ALLOW_DATA_LOSS) |
This command runs the DBCC CHECKDB utility again, but this time with the REPAIR_ALLOW_DATA_LOSS option. This option attempts to repair any detected corruption, but it can result in data loss because it may delete or modify corrupted data to make the database functional again.
f. Return the database to normal operation (multi-user mode).
| ALTER DATABASE [YourDatabase] SET MULTI_USER |
This command sets the database back to multi-user mode, which allows multiple users to connect and use the database as normal.
4. After Execute the script refreshes the database.
For any queries, you can reach us at support@knowband.com. Knowband provides best-in-class solutions for everything eCommerce. We also offer custom development of all sorts like Plugins and Mobile apps for Prestashop, and Opencart. Magento and Magento 2. Click here to know more.
Recommendations for you:
We highly recommend our No Code Mobile App solution to all eCommerce store owners. Know more:
