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
3. Overwate this newly created database with the Suspect database
4. Restart SQL Server
5. At this time, the newly created name database will appear, and the following statement is performed correctly (pay attention to modify the database name)
Use mastergo
SP_Configure 'Allow Updates', 1 Reconfigure with Overridego
Update sysdatabases set status = 32768 Where name = 'His222'go
sp_dboption 'Test', 'Single User', 'True'go
DBCC CHECKDB ('Test') Go
Update sysdatabases set status = 28 where name = 'test'go
sp_configure 'allow updates', 0 Reconfigure with Overridego
sp_dboption 'Test', 'Single User', 'False'go
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.
If you do not add a database status, you guide the database into a new library to replace the old library.
Enterprise Manager - Right-click Your Database - All Tasks - Export Data - Target Database Select New - Select "Copy Objects and Data between Two SQL Database -" Contains Extension Properties " Other options as needed - finally completed
