"Suspect" in SQL Server 2008R2 database causes no access

When working with SQL Server relational databases on a daily basis, there are times when the database (for example, SharePoint site configuration database name Sharepoint_config) is not functioning properly, such as the database stopping the database at read-write time, resulting in SQL The server database is not properly interrupted, and when the database is opened again, some databases will be marked as "suspect" (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 sharepoint_config SET EMERGENCY

2. Turn the database into single-user mode

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.

DBCC CheckDB (Sharepoint_config, Repair_allow_data_loss)

4. Turn the database back into multi-user mode

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, the database that is marked "suspect" when you open SQL Server is restored to its normal state.

"Suspect" in SQL Server 2008R2 database causes no access