Sqlserver-dba.com

Recover from a Suspect database

--Recover from a Suspect db on SQL Server 2005 Standard Service Pack2
---Error: 3414, Severity: 21, State: 1.
--During redoing of a logged operation in database 'MY_DB', an error occurred at log record ID (5006:4238:75).
--Typically, the specific failure is previously logged as an error in the Windows Event Log service.
--Restore the database from a full backup, or repair the database.
--I progressed with these steps , to get the db back to an ONLINE state
--NOTE : This is a last resort , and I only tried , once I'd exhausted recovery from backup etc

ALTER DATABASE MY_DB SET ONLINE;
GO
DBCC CHECKDB (MY_DB, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS;
GO
ALTER DATABASE MY_DB SET EMERGENCY;

GO
DBCC CHECKDB (MY_DB, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS;
GO
ALTER DATABASE MY_DB SET SINGLE_USER;
GO
DBCC CHECKDB (MY_DB, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS;
GO
ALTER DATABASE MY_DB SET MULTI_USER;
GO 
SELECT state_desc FROM sys.databases WHERE name='MY_DB';
Author: Jack Vamvas (http://www.sqlserver-dba.com)

Author: Jack Vamvas (http://www.sqlserver-dba.com)

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment


sqlserver-dba.com | SQL Server Performance Tuning | SQL Server DBA:Everything | FAQ | Contact