bug: data file autogrowth set to 12800%

[XNMB]

SQL2K5 SP1

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?

thanks

[Andrea Montanari]

hi,
XNMB wrote:

SQL2K5 SP1

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?

unfortunately, it's a bug, already reported as you can see at
http://lab.msdn.microsoft.com/produc...2-729b178a7fa0
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

[Erland Sommarskog]

XNMB (Ch***************@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/Produc...ckId=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, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx