Posted by Erland Sommarskog on 05/11/06 15:38

XNMB (ChristianBautista@gmail.com) writes:
> the autogrowth setting in one of my database's primary filegroup data
> file keeps having the value of 12800%, which was originally set to
> 100MB, everytime the service is restarted. the same occurs whenever i
> restore a backup of this database in our development environment.
>
> WTF? this issue does not happen to other filegroups. only on the
> primary data file. whenever this happens the 4GB data file grows to
> more than 70GB (even the math is incorrect) with about 95% of UNUSED
> space.
>
> has anyone else come accross this BS or anyone knows how to prevent
> this from happening? is MS aware of this not-so-funny joke?

Yes, as Andrea said, this is a known issue.

It appears that the problem appears with databases from SQL 2000, and it's
old bug that causes problems.

Look at http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackId=FDBK49455
for a way to fix the database while its on SQL 2000.

If the database is on SQL 2005, it may help to set an explicit growth to
a fixed size.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]