home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.ms-sqlserver      Notorious Rube Goldberg contraption      19,505 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 18,810 of 19,505   
   Query Builder to Erland Sommarskog   
   Re: Help with shrinking a database   
   10 Jan 13 13:54:02   
   
   From: querybuilder@gmail.com   
      
   I have this issue with one of my Database. I have a database which is TDE   
   enabled. I did a data purge of one of the table which was holding several   
   million rows of data. Normally I dont shirnk the database but this time, its   
   alot of space and is    
   increasing the backup size because of TDE. Now I want to release the space to   
   the Drive. I have tried several ways to shrink:   
   I tried thru the GUI and it just closes but doesnt shrink   
   I tried thru the GUI to release only a few GBs but nothing is changing.    
   I tried thru Query window, no luck.    
      
   Is there a problem shrinking Database which are TDE enabled? I ran into an   
   issue with one of my other DB which is also TDE Enabled..    
      
   Any help would be much appreciated...    
      
   Thanks in advance..    
   Aravin Rajendra.    
      
      
   On Thursday, January 10, 2013 2:58:40 PM UTC-5, Erland Sommarskog wrote:   
   > Dom (dolivastro@gmail.com) writes:   
   >    
   > > I don't want to kill it, because I think I might lose data.  How do I   
   >    
   > > get out of this?   
   >    
   >    
   >    
   > You can kill it; it is transactional.   
   >    
   >    
   >    
   > And there is a very simple way to avoid that this happens again: stop   
   >    
   > shrinking your database! Shrinking a database that is going to grow   
   >    
   > again is completely pointless. Shrinking is something you should use   
   >    
   > only exceptionally. For instance, you take a copy of a production database   
   >    
   > for development, but delete most of the data. Or you have had some   
   >    
   > accident that inflated the database.   
   >    
   >    
   >    
   > Shrinking introduces lots of defragmentation, so you need to run    
   >    
   > reindexing once shrink has completed (or you have stopped it). And   
   >    
   > since reindexing needs free space, the database might grow again...   
   >    
   >    
   >    
   >    
   >    
   > --    
   >    
   > 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)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca