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

Suspect Mode in Sql Server 2008 Expand / Collapse
Author
Message
Posted Tuesday, August 21, 2012 1:46 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 13, 2014 2:10 AM
Points: 3, Visits: 15
What is the cause of database in suspect mode and how to overcome from it?
Post #1347614
Posted Tuesday, August 21, 2012 2:06 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, November 3, 2014 8:05 AM
Points: 1,191, Visits: 9,892
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.
Post #1347624
Posted Tuesday, August 21, 2012 2:21 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: Yesterday @ 1:14 PM
Points: 40,615, Visits: 37,081
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 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 #1347628
Posted Tuesday, August 21, 2012 2:39 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 13, 2014 2:10 AM
Points: 3, Visits: 15
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...
Post #1347633
Posted Tuesday, August 21, 2012 2:44 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, November 3, 2014 8:05 AM
Points: 1,191, Visits: 9,892
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.
Post #1347638
Posted Tuesday, August 21, 2012 2:47 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: Yesterday @ 1:14 PM
Points: 40,615, Visits: 37,081
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 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 #1347639
Posted Tuesday, August 21, 2012 9:11 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, November 6, 2014 8:19 PM
Points: 121, Visits: 1,251
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

SQL Database Recovery Expert
Post #1348157
Posted Tuesday, August 21, 2012 10:11 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 13, 2014 2:10 AM
Points: 3, Visits: 15
Thanks
Post #1348171
Posted Wednesday, August 22, 2012 1:19 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: Yesterday @ 1:14 PM
Points: 40,615, Visits: 37,081
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 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 #1348210
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse