January 25, 2011 at 5:16 am
What are the best practices if the Database goes into a Suspect Mode?
NEVER NEVER EVER GIVE UP;-)
January 25, 2011 at 5:46 am
Gail has an excellent article on this.
http://www.sqlservercentral.com/articles/Corruption/65804/"> http://www.sqlservercentral.com/articles/Corruption/65804/
I know that you're asking specifically about the suspect state (she avoids getting into that discussion in this article); however, your question is very broad so you may benefit from her discussion about database corruption in general.
January 25, 2011 at 5:51 am
1) Don't panic
2) Don't detach the DB
3) Don't restart SQL
4) Check the SQL error log for the reason that the DB was marked suspect and plan a recovery based on that.
Theoretical question?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 11:03 pm
Yes
So if one of my log file is missing then the database goes into the suspect mode.
So what other reasons can cause the database to go into the suspect mode?
NEVER NEVER EVER GIVE UP;-)
January 26, 2011 at 12:53 am
scorpianprince (1/25/2011)
So if one of my log file is missing then the database goes into the suspect mode.
No, it won't. If the log file is missing, SQL will either recreate the log or mark the database recovery pending.
('one of my log files'? There should only ever be one log file)
So what other reasons can cause the database to go into the suspect mode?
Corruption encountered during a rollback or roll-forward process.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply