From: esquel@sommarskog.se   
      
   Query Builder (querybuilder@gmail.com) writes:   
   > database_name     database_size     unallocated space   
   > A_DB              411324.00 MB     196982.09 MB   
   >   
   > reserved     data              index_size     unused   
   > 215290792 KB     192933232 KB     14584032 KB     7773528 KB   
      
   So of a total database size of 215 GB, you have 7 GB of unused space.   
   This database does not need to shrink - it needs to grow. Exactly   
   how much depends how data you add to if of course. But the key is   
   that, while there is an autogrow function, it is nothing you should   
   rely on, but the database show be pre-grown in a controlled fashion.   
      
   Out of the blue, I would suggest adding 50 GB of breathing space.   
      
   > The issue I am facing is that one of the Data file (A_DATA) is sitting   
   > on a drive which is 90% filled and We cleared a log table that was   
   > holding about 90GB space out of this file. I want to release the space   
   > to that drive. This particular data file is set to not grow.   
      
   Well, you might have deleted 90 GB of data, but that does not show in   
   the numbers above. Is that log table by chance a heap?   
      
   --   
   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)