Q

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 first published in October 2005
This Content Component encountered an error

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

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.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchBusinessAnalytics

SearchDataCenter

SearchDataManagement

SearchAWS

SearchOracle

SearchContentManagement

SearchWindowsServer

Close