Separate the database first
Enterprise Manager - Right-click Suspect's Database - All Tasks - Separate Database
Then back up your SUSPECT database file, then follow the steps below:
1. Create a newly named database
2. Stop SQL Server again (Be careful not to separate the database)
3. Overwate this newly built database with the original database data file
4. Restart SQL Server
5. At this time, you will be suspicious when you open the Enterprise Manager. Whether you do this, you will do the following statement (pay attention to the database name)
6. The data in the database can be accessed after completion. At this time, the database itself is generally issued, the solution is to create a new database using the database's script and will pass the data.
Use mastergo
SP_Configure 'Allow Updates', 1 Reconfigure with Overridego
Update sysdatabases set status = 32768 where name = 'quoted database name' Go
SP_DBOPTION 'Troubleshooting Database Name,' Single User ',' True'go
DBCC CHECKDB ('Troubleshooting Database Name) GO
Update sysdatabases set status = 28 where name = 'quoted database name' Go
sp_configure 'allow updates', 0 Reconfigure with Overridego
SP_DBOPTION 'Troubleshooting Database Name,' Single User ',' True'go
