A Timeout Occurs When a Database Is Automatically Expanding

Article ID : 305635
Last Review : December 2, 2005
Revision : 3.1
http://support.microsoft.com/kb/305635/
I have SQL Server 2000 Enterprise Edition and have the some reported issue
in the above article, the article says that it applies to Standard Edition,
does it mean that itâ's not the same problem I have?
Hope some one can answer me quickly..
ThanksThe article applies to all SQL 2000 editions. Timeout's occur on the client
side and it can take time for SQL Server to expand files regardless of the
SQL Server 2000 edition.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Murad Hashem" <Murad Hashem@.discussions.microsoft.com> wrote in message
news:87A2DAEE-5CEA-44C8-BFDD-B726955FADE8@.microsoft.com...
> Article ID : 305635
> Last Review : December 2, 2005
> Revision : 3.1
> http://support.microsoft.com/kb/305635/
> I have SQL Server 2000 Enterprise Edition and have the some reported issue
> in the above article, the article says that it applies to Standard
> Edition,
> does it mean that it's not the same problem I have?
> Hope some one can answer me quickly..
> Thanks
>|||Murad
As an aside to your existing problem. You would be better off controlling
the growth of your database manually.
Auto grow is good as a fall back but a better way is to monitor your
database growth and anticpate your growth requirements before they occurr.
That way you can allocate an amount of extra space that will be sufficiant
for 9 to 12 months (disk space allowing of course) rather than a typical 10%
(or similar) that people tend to use for auto grow.
Databases using auto grow typically tend to grow more regularly than
databases that are monitored and manually increased. This can mean
fragmentation at the disk level, that can lead to bad performance. Also if
you do it manually you can schedule it at a quite time, not in the middle of
your business day, which always seems to happen with autogrow. Doing outside
your main business hours will reduce the impact on your users.
Another thing is to have an archive strategy for all your databases. I work
for a large bank and we will not let a database go into production if it does
not have an archive strategy. Do this with your systems and after the first
year or two, you rarely (or in some cases never) have to expand your
databases again.
HTH
John
"Murad Hashem" wrote:
> Article ID : 305635
> Last Review : December 2, 2005
> Revision : 3.1
> http://support.microsoft.com/kb/305635/
> I have SQL Server 2000 Enterprise Edition and have the some reported issue
> in the above article, the article says that it applies to Standard Edition,
> does it mean that itâ's not the same problem I have?
> Hope some one can answer me quickly..
> Thanks
>