mssql2000 Database Suspect resolution

1. Create a new database with the same name
2. Stop SQL Server again (be careful not to detach the database)
3. Overwrite the new database with the data file of the original database
4. Restart SQL Server
5. When you open Enterprise Manager, you will be questioned, regardless, execute the following statement (note that the database name is modified)
6. After completion of the general access to data in the database, at this time, the database itself is generally a problem, the solution is to use the database script to create a new database, and the data in the line.

Use MASTER
GO

sp_configure ' Allow UPDATES ', 1 RECONFIGURE with OVERRIDE
GO

UPDATE sysdatabases SET STATUS =32768 WHERE name= ' suspect database name '
Go

sp_dboption ' suspect database name ', ' Single user ', ' true '
Go

DBCC CHECKDB (' Suspect database name ')
Go

Update sysdatabases set status =28 where Name= ' suspect database name '
Go

sp_configure ' allow updates ', 0 reconfigure with override
Go

sp_dboption ' suspect database name ', ' Single user ', ' false '
Go