SQL Server Administration: You can try to save data by creating an empty database and copying tables to it after placing the database into EMERGENCY and then SINGLE_USER state. Most of the time, a suspect database has to be restored to be able to be used again. However, sometimes it is possible to repair a suspect database. I recently did just that for a client, and recovered 4 suspect databases.
— Attempt repair suspect database
— Set database in EMERGENCY read only state
ALTER DATABASE MyDB SET EMERGENCY
— Set database in SINGLE_USER state
ALTER DATABASE MyDB SET SINGLE_USER
DBCC CHECKDB(MyDB) WITH NO_INFOMSGS — Run integrity Check
— DBCC CHECKDB (MyDB, REPAIR_REBUILD) WITH NO_INFOMSGS — Repair database with no dataloss
— DBCC CHECKDB (MyDB, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS — Repair database with possible dataloss
— Set database in MULTI_USER state
ALTER DATABASE MyDB SET MULTI_USER
Please log in again. The login page will open in a new window. After logging in you can close it and return to this page.