• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

percent filegrowth settings

can I ask what risks/issues are caused by using percent filegrowth settings? Please keep answer tech free management freindly if possible? Healthcheck scanners say this setting can lead to out of control filegrowth, why so?
0
pma111
Asked:
pma111
4 Solutions
 
YZlatCommented:
it's not bad for small databases, but when database is rather large, even 10-15% growth can cause performance issues
0
 
PadawanDBAOperational DBACommented:
I usually recommend actual size amounts (512 MB, 1024 MB, etc.).  The reason for this being that as the database grows larger it will grow by larger and larger amounts.  If you don't have some settings set on your database server (what's called instant file initialization), this can cause all activity in the database to stop until it is done growing the file(s).

My best advice is to make the size of the data files as large as they need to be to handle growth up to a point in time where you would migrate the database(s) to new hardware and allow for the filegrowth as a last resort.  I say last resort because I absolutely don't advise anyone to disable filegrowth because it will essentially offline your database if you hit the limit and it can't grow.

Edit:

Forgot to mention that when you decide how much you want your database to grow in the event that it needs to autogrow, you introduce physical fragmentation every time it auto grows, so you will want to make it grow by a large enough size that it doesn't happen often (or at least gives you time to address the issue)
0
 
Steve WalesSenior Database AdministratorCommented:
The reason it can cause out of control file growth is because it's not growing by a percentage of the size of the file at the time it was created, but by the current size.

So you start with 100GB with 10% growth.  After the first grow, you're at 110GB.  Next time you're at 121 GB, then 132.1 GB etc.  Each growth gets a little larger.

If you set larger growth percentages, it's obviously worse:

100 GB at 50% - 150 GB - 225 GB - 332.5 GB etc.

As mentioned above, not so much of an issue on smaller databases, but on larger databases with larger growth percentages it can be an issue.

Autogrowth vs No autogrowth is also an argument I've seen discussed many times in both the SQL Server and Oracle technical forums.

I always monitor freespace in my databases carefully so that I can control growth on my terms in a manner and timeframe that suits me - so I try to avoid databases auto growing by themselves - but the feature is still turned on.
0
 
Scott PletcherSenior DBACommented:
I suggest never using percentage growth.  I've found it to be slower than a fixed amount.

Change the size settings on the model db to a fixed amount of what a "typical" db in your environment would need.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now