SQL Server 2005/2008 database is marked as "suspect"/"questioned"

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, follow the steps below to resolve the problem, open the SQL Query Editor window in the database and run the following command.
1, modify the database for emergency mode

1 ALTER DATABASE sharepoint_config SET EMERGENCY

2. Turn the database into single-user mode

1 ALTER DATABASE sharepoint_config 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.

1 DBCC CheckDB (sharepoint_config, Repair_allow_data_loss)

4. Turn the database back into multi-user mode

1 ALTER DATABASE sharepoint_config SET multi_user

5. Start-to-run input cmd-> open the DOS command window and enter the following command to restart the database service
Net stop MSSQLSERVER--stop service
Net start MSSQLSERVER--Start service
Again, when you open SQL Server 2005, the database that is marked as "suspect" is restored to its normal state.

Note:

If the amount of data is large, it is important to note that the tempdb database will take up disk space with the repair, the default tempdb is the system disk, if the system disk is not large enough to repair the failure, you can consider moving the tempdb database to disk space is not large

SQL Server 2005/2008 database is marked as "suspect"/"questioned"