Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Does anyone know of any issues (performance or otherwise) associated with a FILEGROWTH setting as a % rather than as a fixed size? What advantage is there to % over fixed increments?
Using a percentage can mean big autogrows. When you are adding 10% to a 100GB DB, you’re adding 10GB. If that takes longer than 30 seconds (it easily can) and you have a caller with a 30s timeout that will cause a rollback, you’ll end up with a lot of disk activity for a long time if you have a retry loop. I might know someone a variant of this scenario happened to 😛
In general, make sure to be very careful with autogrows – they should be there as a last resort, not as a primary growth management strategy. For any production database of consequence you should be managing growth by ensuring there is sufficient headroom during a maintenance window.