File growth problem in 2005

Have a database, one filegroup with one datafile and one log file.

However, restarted the box and saw that the growth settings for the datafile was changed from 100Mb increments to 25600%. The logfile is still the same at 200Mb as required. Both have unlimited growth.

Looking at sysfiles in the database, growth is 25600 for the log and data file. In Management Studio I cannot change the setting for the data file (log file still shows 200Mb growth increments), Studio tells me "Value 25600 is not valid for Value. Value should be between Minimum and Maximum.

Any thoughts? Cant really have a database sitting with this growth rate, and cannot change the value in sysfiles either (even with sp_configure etc).

Any ideas? Thanks

Have you tried clicking on the button next to the text that describes the growth. This provides the means to change the growth settings. The button has ellipse on it ...|||Seems to be a GUI problem. Try changing the autogrow value using ALTER DATABASE instead.

--

Tibor Karaszi, SQL Server MVP

http://www.karaszi.com/sqlserver/default.asp

http://www.solidqualitylearning.com/

Blog: http://solidqualitylearning.com/blogs/tibor/

wrote in message

news:19115900-bfb9-4dff-8042-9b7462a44781@.discussions.microsoft.com...

> Have a database, one filegroup with one datafile and one log file.

>

> However, restarted the box and saw that the growth settings for the

> datafile was changed from 100Mb increments to 25600%. The logfile is

> still the same at 200Mb as required. Both have unlimited growth.

>

> Looking at sysfiles in the database, growth is 25600 for the log and

> data file. In Management Studio I cannot change the setting for the data

> file (log file still shows 200Mb growth increments), Studio tells me

> "Value 25600 is not valid for Value. Value should be between Minimum and

> Maximum.

>

> Any thoughts? Cant really have a database sitting with this growth rate,

> and cannot change the value in sysfiles either (even with sp_configure

> etc).

>

> Any ideas? Thanks

>

>|||

yeah, it's a GUI problem preventing me to change that value (I got that error from clicking the ... button to change it).

My other worry is what changed this, the system was set to grow in increments of 100Mb, settings omething to 25600% increase (when you cant even get to that value in the GUI) means something on the server changed ther settings.

|||This seems to be a bug on the SQL engine. I've had it happen twice now. First time I assumed I had done something wrong, reset the autogrow values to a number. This morning it has happened again and the server has no disk space left. 100% sql engine bug I think.|||

Further to this see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

The only workaround I have so far is to set Max size of the file to prevent the file from growing too large, or to turn off AutoGrow