MS SQL Server - restricted file growth setting

Author

restricted file growth setting

mp3nomad

2006-03-27, 3:23 am

I'm using SQL Server 2005 std on a Windows 2003 server and have noticed that
some of the databases have changed the log file growth setting from unlimited
growth to restricted growth of 2,097,152 mb. Is this a bug? Some of my
databases that were set to "by 10% unlimited growth" are now "by 10%
restricted growth" and the setting is 2,097,152 mb. I can't seem to change
back to unlimited file growth. I know they shouldn't really be set to
unlimited file growth but some were set that way after migrating from SQL
2000. Sometimes one of the databases changes the data file growth to 1280
percent from 10%.

Just seemed to start doing this in the last couple of weeks and we have had
this installed since November. Seems like a bug.

Please let me know if this could be a bug in SQL 2005... if anyone is
actually owning up to that fact. ;-) :-)

Thanks!

Tibor Karaszi

2006-03-27, 7:25 am

2,097,152 MB translates to 2TB, which is the max size for a transaction log file. So, in effect, you
still have the "unlimited" setting and this is only a presentation quirk.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/

"mp3nomad" < mp3nomad@discussions
.microsoft.com> wrote in message
news:BFE13BE5-9315-4FAC-ADA6- BEAB528F1D37@microso
ft.com...
> I'm using SQL Server 2005 std on a Windows 2003 server and have noticed that
> some of the databases have changed the log file growth setting from unlimited
> growth to restricted growth of 2,097,152 mb. Is this a bug? Some of my
> databases that were set to "by 10% unlimited growth" are now "by 10%
> restricted growth" and the setting is 2,097,152 mb. I can't seem to change
> back to unlimited file growth. I know they shouldn't really be set to
> unlimited file growth but some were set that way after migrating from SQL
> 2000. Sometimes one of the databases changes the data file growth to 1280
> percent from 10%.
>
> Just seemed to start doing this in the last couple of weeks and we have had
> this installed since November. Seems like a bug.
>
> Please let me know if this could be a bug in SQL 2005... if anyone is
> actually owning up to that fact. ;-) :-)
>
> Thanks!

Sponsored Links