b27b31a0   
   XPost: microsoft.public.sqlserver.server   
   From: esquel@sommarskog.se   
      
   Bill E. Hollywood, FL (behrreich@compuserve.com) writes:   
   > I'm not sure how large the database will be for just data, but I am   
   > expecting three or four thousand document uploads per month once   
   > things get going.  Therefore, the file storage and retrieval component   
   > will not be trivial.  It's hard to say how large the documents might   
   > be because they could be in many formats.  Let's assume an average of   
   > 500 kB per document and about 4,000 documents per month -- that gives   
   > us 2GB per month of just document storage.   
      
   500 kB appears a tad high to me, but that is just gut feeling.   
      
   But even if we accept this number - after three years the database   
   will be 72 GB - provided that documents are kept "forever" and not   
   archived anywere.   
      
   To be honest, I am not sure that this warrants a more complex solution   
   to make it easier to have a development database, unless are other reasons   
   you want a document-less database for development. True, restoring   
   72 GB takes longer time than restoring 1GB, but it's not an operation   
   I expect you do very often.   
      
   --   
   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)