Timeline for Shrink database or DB files not reducing size even after dropping biggest table
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 25, 2016 at 20:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 25, 2016 at 0:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 20, 2016 at 15:35 | answer | added | Jon of All Trades | timeline score: 1 | |
| Jul 14, 2015 at 15:22 | comment | added | Aaron Bertrand | Not necessarily - depends on the data, data types, nullability, and fragmentation over time... number of rows is related but not a mathematical truth. | |
| Jul 14, 2015 at 15:21 | comment | added | Joe_Hendricks | @AaronBertrand: Nope. 63GB is the new table with 7M rows. My point there was that, if a 7M table with exactly the same schema (and no indexes) took up 63GB, then a 138M-row table must be exponentially bigger. | |
| Jul 14, 2015 at 15:17 | comment | added | Aaron Bertrand | So it grew to 550 GB, you removed 63 GB and it only went down by 40 GB when you shrank. So you want that other 23 GB removed too. You're telling me your database won't grow 4%? Or even being generous, and shrinking to remove all of the 53 GB of unused space, 10%? I still find that hard to believe. Consider that shrinking and growing files is expensive and disruptive, and weigh that against the benefit of reclaiming a little bit of disk space (relatively), and only temporarily. You should re-think what you're trying to accomplish and why. | |
| Jul 14, 2015 at 15:14 | comment | added | Kin Shah |
I then ran SHRINKDATABASE and SHRINKFILE - why would you do both shrink database and file ? Even if you have to shrink your database (keeping in mind that it wont grow and this caution), use SHRINKFILE.
|
|
| Jul 14, 2015 at 15:14 | comment | added | Joe_Hendricks | The database will grow again, but not to that size. Most of the tables have historical data from previous years. In this case, it had data from 2013, which we don't use. | |
| Jul 14, 2015 at 15:12 | comment | added | Aaron Bertrand | Is the database never going to grow again? If it is, why are you going to reclaim that space just so the database can occupy it again? Will you lease it out short-term? | |
| Jul 14, 2015 at 15:10 | review | First posts | |||
| Jul 14, 2015 at 15:41 | |||||
| Jul 14, 2015 at 15:09 | history | asked | Joe_Hendricks | CC BY-SA 3.0 |