From: anton.txt@g{oogle}mail.com   
      
   Hello, all   
      
   I am working on an in-house backup solution for our MSSQL   
   databases, and have found that a differential backup may   
   take considerable space (around 1 Mb) even if /no/ changes   
   have been made to the database since the previous full   
   backup. Is it possible somehow, before making another   
   differential backup, to check whether it makes sense, i.e.   
   whether the database has changed since the previous (full or   
   differential) backup? In fact, I do not need a criterium,   
   and a mere necessary condition will suffice.   
      
   I want to make sure that my differential backups are not   
   useless.  One solution is to compare byte-for-byte each new   
   diff. backup with the previous one, and delete the copy if   
   it turn out redundant, but I wondered if there were a   
   simpler method.   
      
   --   
   ()  ascii ribbon campaign -- against html e-mail   
   /\  www.asciiribbon.org   -- against proprietary attachments   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)