Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We were saving unnecessary logging data in our database. One table grew to 1 million records, 99% of that is now gone.

We have db size of 40gb and freespace of 24gb.

Whats the best way to regain that space (and consequently reduce the size of our back ups).

Our recovery mode is simple. Can we just use the auto shrink setting in management studio ?


Probably worth noting that there was no need to shrink the DB to reduce the size of backup. Just removing the data is good enough. Our backups are now 9gb.

share|improve this question
up vote 4 down vote accepted

Yes, right click the database -> tasks -> shrink -> database.

share|improve this answer
lol, its auto shrink that I should avoid right. ? I don't need to detach or anything ? – NimChimpsky Mar 29 '12 at 14:12
Normally, shrinking a production db has consequences. Brent Ozar is likely to appear from nowhere and slap you upside the head. But what were talking about here is a change in the nature of application, so I think it's warranted. – Joel Coel Mar 29 '12 at 14:26
Yep, no need to detach or anything like that. Always make sure you have backups just as with anything else. – murisonc Mar 29 '12 at 14:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.