Tags: database, databases, file, growth, log, microsoft, mysql, oracle, restricted, server, setting, sql, std, windows

restricted file growth setting

On Database » Microsoft SQL Server

2,485 words with 1 Comments; publish: Mon, 02 Jun 2008 00:23:00 GMT; (250218.75, « »)

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!

All Comments

Leave a comment...

  • 1 Comments
    • 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.sqlserver.todaysummary.com.discussions.microsoft.com> wrote in message

      news:BFE13BE5-9315-4FAC-ADA6-BEAB528F1D37.sqlserver.todaysummary.com.microsoft.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!

      #1; Mon, 02 Jun 2008 00:24:00 GMT