August 21, 2012 at 1:46 am
What is the cause of database in suspect mode and how to overcome from it?
August 21, 2012 at 2:06 am
Most likely to be corruption of some sort and you may ultimately need to restore from a backup. I'm no expert on the subject (you want to wait for Gail for that), but the advice I'd give until the experts arrive is:
Look in the error log - it will tell you the error that made the database "suspect" - post the errors here.
Don't restart the server without knowing what you're doing.
August 21, 2012 at 2:21 am
SQL encounters corruption in the data file or log file when rolling back a transaction.
SQL encounters corruption in the data file or log file when running crash recovery.
Typically, restore from backup.
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
August 21, 2012 at 2:39 am
Error Log is as follows:
Date,Source,Severity,Message
08/20/2012 19:45:30,,Warning,[408] SQL Server MSSQLSERVER is clustered - AutoRestart has been disabled
08/20/2012 19:45:30,,Warning,[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
08/20/2012 19:45:30,,Warning,[260] Unable to start mail session (reason: No mail profile defined)
08/20/2012 19:45:30,,Information,[129] SQLSERVERAGENT starting under Windows NT service control
08/20/2012 19:45:30,,Error,[364] The Messenger service has not been started - NetSend notifications will not be sent
08/20/2012 19:45:19,,Information,[432] There are 12 subsystems in the subsystems cache
08/20/2012 19:45:18,,Information,[339] Local computer is MSSQLSERVER running Windows NT 6.1 (7600)
08/20/2012 19:45:18,,Information,[310] 16 processor(s) and 16341 MB RAM detected
08/20/2012 19:45:18,,Information,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
08/20/2012 19:45:18,,Information,[102] SQL Server ODBC driver version 10.00.2531
08/20/2012 19:45:18,,Information,[101] SQL Server MSSQLSERVER version 10.00.2531 (0 connection limit)
08/20/2012 19:45:18,,Information,[100] Microsoft SQLServerAgent version 10.0.2531.0 ((Unknown) unicode retail build) : Process ID 2192
08/20/2012 19:44:54,,Information,[393] Waiting for SQL Server to recover databases...
August 21, 2012 at 2:44 am
There must be something else in the error log or a previous error log that shows the error that caused it to become suspect. The messages you've posted aren't relevant to the problem.
In any case, it sounds like restoring from a backup is going to be the way to resolve this.
August 21, 2012 at 2:47 am
Nothing wrong in there, but since the last message is SQL starting to open the DBs, any useful messages will be after that point.
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
August 21, 2012 at 9:11 pm
This was removed by the editor as SPAM
August 21, 2012 at 10:11 pm
Thanks
August 22, 2012 at 1:19 am
prettsons (8/21/2012)
As HowardW & GilaMonster already mentioned the causes of database suspect mode. Please check this article, it has full solution of the issue: http://data-base-recovery.blogspot.com/2012/03/how-to-repair-sql-server-2008-r2.html
Not to be nasty, but that article is bad advice. Emergency mode repair is the last resort for fixing suspect databases, not the first step.
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 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply