SQL SERVER database is flagged as a "suspect" workaround

Issue background:
When working with SQL Server 2005 relational databases on a daily basis, it is sometimes unusual for a database (such as SharePoint site configuration database name Sharepoint_config) to stop the database for no reason, such as when the database is read and write, resulting in SQL Server 2005 the database is not properly interrupted, when the database is opened again will find some database will be marked as "suspicious" (suspect), that is, the database name with a yellow exclamation point, the database can no longer be opened, but the structure of the database and data content are still there.

Workaround:
When this operation failure occurs in the database, you can resolve this by following the steps below, open the SQL Query Editor window in the database and run the following command.

1, modify the database for emergency mode

ALTER DATABASE SET EMERGENCY

2. Turn the database into single-user mode

ALTER DATABASE SET Single_user

3. Repair the database log rebuild , this command checks the allocation, structure, logical integrity and errors in all database objects. When you specify "Repair_allow_data_loss" as the DBCC CHECKDB command parameter, the program examines and fixes the reported errors. However, these fixes may cause some data loss.

DBCC CheckDB ([dbname], Repair_allow_data_loss)

4. Turn the database back into multi-user mode

ALTER DATABASE SET Multi_user

The database marked as "suspect" has returned to its normal state.

MSDN Reference: Https://msdn.microsoft.com/zh-cn/library/ms176064.aspx

SQL SERVER database is flagged as a "suspect" workaround