October 15, 2013 at 9:15 am
Database is in suspect mode due to full logspace
we already have both last night full and all transaction logs backups
we requested extra space added to the server
what are the good steps in bring database online after we get the extra space?
October 15, 2013 at 10:11 am
A full log will not send a database suspect. If your database is suspect, something else is the cause.
What does the SQL error log say?
What's the exact value for status_desc for this database (from sys.databases)?
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
October 15, 2013 at 12:37 pm
you are right, full log was not the reason database became suspect but
lite speed was blocking while database was trying to recover some transactions
thanks
October 15, 2013 at 12:39 pm
So is it fixed?
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
October 16, 2013 at 8:28 am
yes, its fixed by re-starting windows server and that stopped the litespeed that is causing the issue with the database
thank
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy