Method 1
1. Create a database with the same name
2. Stop sqlserver again (do not detach the database)
3. overwrite the new database with the data file of the original database.
4. Restart sqlserver.
5. When you open the Enterprise Manager, there will be a doubt. Ignore it and execute the following statement (note that you must modify the database name)
6. After completion, You can generally access the data in the database. At this time, the database itself usually needs problems. The solution is to use
The database script creates a new database and imports the data.
USEMASTER
GO
SP_CONFIGURE 'allowupdates', 1 RECONFIGUREWITHOVERRIDE
GO
UPDATESYSDATABASESSETSTATUS = 32768 WHERENAME = 'questionable database name'
Go
Sp_dboption 'questionable database name', 'singleuser', 'true'
Go
DBCCCHECKDB ('questionable database name ')
Go
Updatesysdatabasessetstatus = 28 wherename = 'suspicious database name'
Go
Sp_configure 'allowupdates', 0 reconfigurewithoverride
Go
Sp_dboption 'questionable database name', 'singleuser', 'false'
Go