Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Suspect Mode Expand / Collapse
Author
Message
Posted Tuesday, August 14, 2012 6:29 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: 2 days ago @ 8:53 AM
Points: 411, Visits: 1,310
Scott D. Jacobson (8/2/2012)
1. EXEC sp_resetstatus 'DBName'

GO
ALTER DATABASE DBName SET EMERGENCY
DBCC checkdb('DBname')
ALTER DATABASE DBName SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB ('DBName')

2. ALTER DATABASE DBName SET MULTI_USER

If you can't do that you're probably completely hosed. It's time to restore your last known good backup.


Scott

Just curious ...

If the db was actually 2005 or up, what your advice was going t be after running the DBCC ?
Post #1345096
Posted Wednesday, August 15, 2012 1:42 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 40,208, Visits: 36,617
Depends on the results of the checkDB, but the best thing would still be to restore from a clean backup. Emergency mode repair is a last resort for when there is no backup.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1345144
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse