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 have a script that we use for client conversions that deletes all date from almost every table from a database. We do this so that we can clear out any data not related to the application configuration, so that we can start to import data again (test conversions).

Would it be wise to shrink the DB after that process?
Will the continued cycle of import data-->delete data-->import data-->delete data cause fragmentation and "artificial growth" of the DB size?

Thanks in advance

share|improve this question

Log file shrinks are ok with runaway log files. Data file shrinks, not so good. To quote Paul Randal (former owner of the shrink code):

" file shrink causes massive index fragmentation."

Have a read through his post about shrinking log and data files. Pretty much sums it up.

share|improve this answer

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.