Database AutoGrowth

SQL Server Database AutoGrowth

Leaving the default settings for SQL Server AutoGrowth is an unhealthy practice.  As many will agree, the default growth rates should be changed .

OK.  So using percentage settings is a bad practice.  I don’t want to grow the database in 1 MB increments, and not touching it is bad too.  What am I supposed to do?  How can I best configure my SQL Server AutoGrowth settings?  Are there any best practices or recommendations for database autogrowth?   Aggghhhhhh!

Before I pull out my hair, let me digress…

Over the course of time, colleagues and experience have helped me draw up some general guidelines:

  • If the file size is less than 1 GB , then set the File Growth Rate for the data file to 200 MB .
  • If the file size is between 1 GB and 200 GB , then set the File Growth Rate for the data file to 1 GB .
  • If the file size is greater than 200 GB , then set the File Growth Rate for the data file to 10 GB .

The conditions in your environment may vary, but this is a good place to start.  Consider whether your database is a data warehouse, has a transactional focus, or very large database (VLDB).  Your goal is to minimize the number of times your database grows, but when it does, take the amount of storage you need without having to return to claim more too soon.

The final piece of advice, as any good DBA will tell you, is interview your users, measure your workload, monitor your database growth, and adjust settings for your specific situation.

Leave a Reply