From: esquel@sommarskog.se   
      
   mat (mat@notarealdotcom.adr) writes:   
   > 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.   
      
   So there is a stack dump in the log? The stack dump is not entirely   
   easy to read, but usually there is some indication of the statement   
   that was issued. Also, the date and time for the accident may give   
   some indication.   
      
   Maybe you have a maintenance job set up and something went wrong during   
   this job. Why something would go wrong all of a sudden? Bad hardware is   
   a common reason.   
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)