Sql Server数据库被置疑解决方法（国外英文资料）.doc

Sql Server数据库被置疑解决方法（国外英文资料） First confirm the backup. MDF and.ldf files. Create a new database of the same name in SQL Server and stop the SQL Server service. Use the original.mdf and.ldf files to cover the corresponding new database. MDF and.ldf files. Restart the SQL Server service, which should be seen as Suspect. Execute the following commands in the SQL query analyzer to allow the update system table to be updated: Use the master The go Sp_configure allow updates, 1 Reconfigure with override The go Set this database as an emergency mode: Update sysdatabases set status = 32768 where name = db_name The go Use the DBCC CHECKDB command to check for errors in the database: DBCC CHECKDB ( db_name ) The GO If the DBCC CHECKDB command fails, go to step 10, otherwise you will set the database as a single-user mode and try to fix it: Sp_dboption db_name, single user, true DBCC CHECKDB ( db_name , REPAIR_ALLOW_DATA_LOSS) The GO If the execution of DBCC CHECKDB (db_name, REPAIR_ALLOW_DATA_LOSS) command prompt said database in single user mode, not restart the SQL Server service, and then continue to try. If the DBCC CHECKDB ( db_name , REPAIR_ALLOW_DATA_LOSS) command fails, go to step 10, otherwise the error in the database is successfully fixed: Re-execute the DBCC CHECKDB ( db_name ) command to confirm that there are no errors in the database. Clear query status of the database: sp_resetstatus db_name Clean up the single-user mode status of the database: sp_dboption db_name, single user, false Restart the SQL Server service, and if all is ok, the database has been successfully restored. If none of these steps solve the problem, please refer to the document in the attachment to try to restore the data in the database by rebuilding the transaction log. If you only have the MDF file, the problem is more complicated, and we need to rebuild the transaction log directly: Create a new database of the same name in SQL Server and stop the SQL Server service. Use the original L