Method One
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 again
5. When you open Enterprise Manager, there will be doubt, regardless, execute the following statement (note modify the database name)
6. After the completion of the general access to the data in the database, at this time, the database itself generally have problems, the solution is to use
The database script creates a new database and guides the data into the line.
Usemaster
Go
sp_configure ' allowupdates ', 1RECONFIGUREWITHOVERRIDE
Go
Updatesysdatabasessetstatus=32768wherename= ' Suspect database name '
Go
sp_dboption ' suspect database name ', ' SingleUser ', ' true '
Go
DBCCCHECKDB (' Suspect database name ')
Go
Updatesysdatabasessetstatus=28wherename= ' Suspect database name '
Go
sp_configure ' allowupdates ', 0reconfigurewithoverride
Go
sp_dboption ' suspect database name ', ' SingleUser ', ' false '
Go
Current 1/2 page
12 Next read the full text
