SQL Server database (suspicious) Solution 4 kinds

Restart Service
--------------------------------------------------
Log file lost, build a log file
--------------------------------------------------
Workaround for SQL SERVER 2005 database status "suspect"
--mydb for the repaired data name
Use MASTER
GO
sp_configure ' Allow UPDATES ', 1 RECONFIGURE with OVERRIDE
GO
ALTER DATABASE MyDB SET EMERGENCY
GO
sp_dboption ' MyDB ', ' Single user ', ' true '
GO
DBCC CHECKDB (' MyDB ', ' Repair_allow_data_loss ')
GO
ALTER DATABASE MyDB SET ONLINE
GO
sp_configure ' allow updates ', 0 reconfigure with override
GO
sp_dboption ' MyDB ', ' Single user ', ' false '
GO
-------------------------------------------------
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 zhangxing SET EMERGENCY

2. Turn the database into single-user mode

ALTER DATABASE zhangxing 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 (zhangxing, Repair_allow_data_loss)

4. Turn the database back into multi-user mode

ALTER DATABASE zhangxing SET multi_user

You can also do this:

1: Re-establish a, same database, path name, file all the same.

2: Turn off SQL Server service;

3: Copy the source files.

4: The SQL Server service is turned on, so the problem is solved.

SQL Server database (suspicious) Solution 4 (RPM)