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,809 of 19,505    |
|    Erland Sommarskog to Dom    |
|    Re: Help with shrinking a database    |
|    10 Jan 13 20:58:40    |
      8fd294a8       From: esquel@sommarskog.se              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