June 15, 2010 at 8:24 am
What internally happens if db goes in suspect mode ?
June 15, 2010 at 8:31 am
SQL sets the database state to suspect (in sys.databases) and prevents anyone from accessing or querying the DB.
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
June 15, 2010 at 9:14 am
I meant exactly what happens that causes suspect mode to db?
June 15, 2010 at 9:31 am
many reasons, mainly :
1. Missing device causes database to be marked suspect.
2. Disk out of space and no space to expand log file.
3. If one or more database files are not available.
4.If the entire database is not available.
5.If one or more database files are corrupted.
6.If a database resource is being held by the operating system.
and could be many more reasons. I could not recollect.
SQL DBA.
June 15, 2010 at 9:41 am
Check your sql error logs. There should be some messages that relate to that database being marked as suspect. Dont do anything until you have done this
June 15, 2010 at 10:55 am
1. Missing device causes database to be marked suspect.
Won't cause suspect, can cause recovery_pending
2. Disk out of space and no space to expand log file.
Will not cause a database to go suspect. Read-only at worst.
3. If one or more database files are not available.
4.If the entire database is not available.
Won't cause suspect, can cause recovery_pending
5.If one or more database files are corrupted.
Will only result in the db going suspect if that corruption is encountered during a rollback/rollforward operation.
6.If a database resource is being held by the operating system.
Won't cause suspect, can cause recovery_pending
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
June 15, 2010 at 10:57 am
beejug1983 (6/15/2010)
I meant exactly what happens that causes suspect mode to db?
SQL will mark a database suspect if and only if corruption (data file or log file) is encountered during a transaction rollback or during restart-recovery when bringing a database online.
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
February 20, 2013 at 9:43 am
Thank you a lot.
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply