Performance & Timeout during auto grow in SQL 2000

We had a downtime in our Stress environement during Database Automatic Data
file grow.
The database was preallocate to 20Gb with auto increment 10%.
It seems the reallocation of the 2 Gb take minutes.
We are trying to get Best Practices in SQL 2000 to see what is recommended.
- Having a Dedicated DBA to check DB space available?
- Use or Not Auto Grow? use % versus fixed size?
The idea here is to get business justification and/or use case to help us
deciding Dedicated DBA versus specific tools & technologie.
Hi
Auto grow should only be a last resort. Create the DB big enough, and then
check on it daily/weekly. You can setup an alert to fire an e-mail off if the
free space gets too low. If you have the space, grow the Db to 30Gb when the
server is not too busy.
Regards
Mike
"Fabrice PIERRE" wrote:

> We had a downtime in our Stress environement during Database Automatic Data
> file grow.
> The database was preallocate to 20Gb with auto increment 10%.
> It seems the reallocation of the 2 Gb take minutes.
> We are trying to get Best Practices in SQL 2000 to see what is recommended.
> - Having a Dedicated DBA to check DB space available?
> - Use or Not Auto Grow? use % versus fixed size?
> The idea here is to get business justification and/or use case to help us
> deciding Dedicated DBA versus specific tools & technologie.
|||Hi ,Mike
I'd go with creating a database big enough with auto-grow feature.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ACB025A7-3ACE-4E3D-9FD2-6695A1C3AAB1@.microsoft.com...
> Hi
> Auto grow should only be a last resort. Create the DB big enough, and then
> check on it daily/weekly. You can setup an alert to fire an e-mail off if
the
> free space gets too low. If you have the space, grow the Db to 30Gb when
the[vbcol=seagreen]
> server is not too busy.
> Regards
> Mike
> "Fabrice PIERRE" wrote:
Data[vbcol=seagreen]
recommended.[vbcol=seagreen]
us[vbcol=seagreen]