auto grow

How expensive is auto grow when it it kicks in? We're planing on monitoring database growth and resizing as needed, but want to set this feature as well. Is it better to set this high (ie 10% on a 5gb database) or low (ie fixed 50 mb)?
thanks
The larger the database the more expensive it becomes. A small DB growing a
little is of course a small expense. It is better to plan ahead for a
larger DB and try to grow it in advance when it will not effect your users.
Still keep auto grow enabled in case you miss a step but try and keep ahead
of it so it does not happen and tick off your user base.
Jeff Duncan
MCDBA, MCSE+I
"Peter Feakins" <anonymous@.discussions.microsoft.com> wrote in message
news:4F1E0506-78D8-4C7C-B3C2-953C5CCE8874@.microsoft.com...
> How expensive is auto grow when it it kicks in? We're planing on
monitoring database growth and resizing as needed, but want to set this
feature as well. Is it better to set this high (ie 10% on a 5gb database)
or low (ie fixed 50 mb)?
> thanks
|||You can find these issues addressed and suggestions on using
autogrow in the following article:
INF: Considerations for Autogrow and Autoshrink
Configuration
http://www.support.microsoft.com/?id=315512
-Sue
On Mon, 3 May 2004 07:56:11 -0700, "Peter Feakins"
<anonymous@.discussions.microsoft.com> wrote:

>How expensive is auto grow when it it kicks in? We're planing on monitoring database growth and resizing as needed, but want to set this feature as well. Is it better to set this high (ie 10% on a 5gb database) or low (ie fixed 50 mb)?
>thanks