c429e28f   
   From: esquel@sommarskog.se   
      
   Ryan (ryanofford@hotmail.com) writes:   
   > This leaves me with a problem. Do I run CHECKDB against live and hope   
   > for the best ? Should I wait until I prepare the new server ? What is   
   > safest and best practice. What if something goes wrong ?   
      
   Just a stupid question: but are there no test machines to which you   
   can restore a backup? This has a number of advantages:   
      
   1) You are testing that your backup works.   
   2) You run DBCC in an offline environment.   
   3) You are testing that your restore works as well.   
      
   I have experienced cases where DBCC did not report errors on the live   
   database, only when I had restored it. (I should hasten to add that this   
   was with SQL 6.0, loooong ago.)   
      
   You said this was a 24/7 shop and if they don't have spare machines or   
   a disaster plan, I get scared.   
      
   When running on a live database, you may prefer to use PHYSICAL_ONLY to   
   reduce the impact.   
      
   You should really run a full CHECKDB on the new server, before you take   
   it live. But you can do that while the old machine is still the production   
   server.   
      
   --   
   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   
   SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)