Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 18,266 of 19,505    |
|    mat to All    |
|    How can I check out the reason a db is i    |
|    26 Apr 11 07:39:22    |
      From: mat@notarealdotcom.adr              This AM a database on my dev box is listed as being in recovery. I       checked the sql server log (in SSMS Management/SQL Server Logs) and all       it says is that there was a serious error. This db was not used for a       couple of days and the machine didn't crash or anything like that so I'm       disturbed that 'somehow' it became broken and I'd like to explore why.              The log I've seen so far just says              Error: 18456, Severity: 14, State: 38.              I can stop the db engine and delete/restore no problem (is a dev copy,       not production) but I'd rather see what else I might be able to learn       from this. What else can I check?              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca