January 26, 2010 at 10:17 pm
MothInTheMachine (1/26/2010)
I'm wondering if that might be something that's going on in my shop. i was going to say I suspect that this is going on but that would have been bad.
A suspect database is offline and unusable. Accessing the DB in any way gets high severity (sev 20 usually) error messages. It's not something that you can have happen and not notice, unless it's to a DB that you never ever use.
Error is something like this:
"Database 'MyDB' cannot be opened. It has been marked suspect by recovery"
Database state is viewable via sys.databases in SQL 2005+ and through the DatabasePropertyEx function in any version 2000+.
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
January 26, 2010 at 10:20 pm
harpistic: I think the most important thing at the moment is to get access to the server so that you can check the Services app and see if SQL is even running. Follow Greg's advice.
Once SQL is up, then you can have a look at the error log, find the exact reason why the database was marked suspect and take appropriate action to fix it.
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
January 27, 2010 at 6:26 am
One other thought -
if the service was running under a domain account, you may want to check and see if the account is locked out.
or try mapping out a drive under this account.
Many times on that platform if the service was not running as Local System, the account had admin rights on the box.
Greg E
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply