Problem solve Get help with specific problems with your technologies, process and projects.

Shrinking database and log files

Shrinking the database or log files to improve SQL Server performance may sound like a good idea, but Monitoring and Administration expert Kevin Kline thinks otherwise and suggests some better alternatives.

Should we shrink the database and log files, or keep the TEMPDB size under check to improve SQL Server performance?
I don't recommend shrinking databases or log files for any production application. The only scenario I think that frequent shrinking of databases and logs are acceptable is on laptop-based applications, such as a sales support application. I would not prevent TEMPDB from growing and would set the growth factor to a substantial amount (in fixed megabyte size) because this reduces the extremely I/O-intensive process of allocating more space to TEMPDB. For example, in one production application, we set TEMPDB to 250 MB by default. We then set TEMPDB to 250 MB in fixed growth for every time it needed to grow.


Do you have comments on this Ask the Expert Q&A? Let us know.
This was last published in October 2005

Dig Deeper on Microsoft SQL Server Installation

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.