SQL SERVER 2005 database suspect fix

ALTER DATABASE suspect DB set emergency
Go
ALTER DATABASE suspect DB set Single_user with rollback immediate
Go
Use master
Go
ALTER DATABASE suspect DB Rebuild Log on
(name=suspectdb_log,filename= ' d:/log/suspect database _log. LDF ')
Go
ALTER DATABASE suspect DB set Multi_user
Go

DBCC CHECKDB (' Suspect database ')
Go

Many of the online is for SQL 2000 not applicable 2005
such as command UPDATE sysdatabases SET STATUS =32768 WHERE name= ' suspect database name '
Not supported in 2005
ALTER DATABASE to suspect DB set emergency

After detection with DBCC CHECKDB, there is a consistency error that can be repaired again with Repair_allow_data_loss.

With exec sp_msforeachtable ' select COUNT (*) from? ' To verify that the tables in the database are truly error-free.

SQL SERVER 2005 database suspect fix