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 123»»»

Database in suspected mode Expand / Collapse
Author
Message
Posted Monday, July 1, 2013 7:46 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 1:22 PM
Points: 1,279, Visits: 1,884
Hello,

Can some one please help

My production database in suspected mode. How can I fix it?

Thank you
Post #1469066
Posted Monday, July 1, 2013 7:51 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: Today @ 11:41 AM
Points: 42,442, Visits: 35,496
What does the SQL error log say?
What backups do you have?



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 #1469068
Posted Monday, July 1, 2013 8:08 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 1:22 PM
Points: 1,279, Visits: 1,884
I have a Redgate backup,[298] SQLServer Error: 4060, Cannot open database requested in login 'DatabaseName'. Login fails. [SQLSTATE 42000]
Post #1469078
Posted Monday, July 1, 2013 8: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: Today @ 11:41 AM
Points: 42,442, Visits: 35,496
There will be messages in the SQL error log saying why the DB was marked suspect. Have a look through the error log, look for messages relating to the database, login failures are uninteresting and useless in identifying the cause.

I didn't ask what you're using for your backups. What backups of this database do you have?



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 #1469083
Posted Monday, July 1, 2013 8:37 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 1:22 PM
Points: 1,279, Visits: 1,884
ldf,mdf,ndf
Post #1469092
Posted Monday, July 1, 2013 8:40 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: Today @ 11:41 AM
Points: 42,442, Visits: 35,496
If you don't want help, that's fine. If you do, please answer my questions. I can't help you without information.


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 #1469093
Posted Monday, July 1, 2013 9:17 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 1:22 PM
Points: 1,279, Visits: 1,884
I have differential from yesterday
Post #1469112
Posted Monday, July 1, 2013 9:20 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: Today @ 11:41 AM
Points: 42,442, Visits: 35,496
Once more with feeling...

Error log entries relating to the database please. SQL will log why the DB was marked suspect. Take a read through the error log and post any error messages relating to the DB (not login failures, they are uninteresting).
What exact backups do you have, full, differential and log? I hope you have more than just a single differential.



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 #1469114
Posted Monday, July 1, 2013 9:26 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 1:22 PM
Points: 1,279, Visits: 1,884
error message,I have differential and full backup

  Post Attachments 
error.docx (29 views, 15.10 KB)
Post #1469118
Posted Monday, July 1, 2013 9:47 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 12:12 PM
Points: 15,517, Visits: 27,896
A database in suspect mode may not be recoverable. That's why Gail is asking about backups. But, to understand what is wrong with the database we need more information than you've provided. Remember, we're not sitting there and can't see what you can see. The error message looks to be from when SQL Server was shutting down at 08:47 this morning. There is an error regarding closing CRS_Financial, but it doesn't indicate the origin of the corruption, which must be elsewhere in your error messages. The error you do have, 9004, indicates a problem with the log. Here is a troubleshooting page from Microsoft Developers Network, MSDN (the documentation for SQL Server) that might help. But we still don't know the original error. That may be in other error logs. It appears you may be starting & stopping the server in an attempt to fix things. Don't do that. Instead, investigate your error logs to see if you can find an error reference to CRS_Financial. But, you may have to go that backup and run a restore. But, if you don't know when the error occurred, you may have backed up the error along with your database.

Just remember, a differential is only good if you also have the full backup that matches with it. Otherwise, you will not be able to restore (unless you also have log backups). But either way, you need to have a "good" backup. This means a backup that doesn't have the corruption in it. Test your restore to a different database and validate that it can come online before you overwrite the existing database.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1469123
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse