Unable to set unrestricted growth on transaction log

  • Hi,

    We have a very strange issue which I have not seen before and after much googling, cannot find any other experiences of this issue.

    We have a SQL Server 2005 Enterprise server (9.00.4207.00) 32Bit running on Windows Server 2003 R2 Enterprise Edition. There are 11 DB's attached but 7 of them we cannot use unrestricted file growth for the transaction logs. When you select unrestricted, click ok, then go back into the properties it says restricted growth to 2097152MB. This is the same for all DB's affected. I know that 2TB is the maximum a transaction log can be, but it seems starnge that it is storing this as a figure rather than leaving it as just unrestricted. The disk we are storing on is 100GB and currently 93GB is free. The transaction log is set to increase by 100MB.

    Can anyone shed any light on this? If you need anymore information, please let me know.

    Thanks,

    Jamie

  • 2TB is the max permissible size for the tran log, so saying that the file is limited to 2TB is the same as saying unrestricted growth.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • There isn't such a thing as "unrestricted" in computing. There are always limits. My guess is the dev team puts in the max number as a way to just have it capped for calculations by the engine. At some point, I'm sure this number will rise, but for this version of DB, that's the max.

  • I agree that the "limit" it is showing is the same as the maximum value SQL can handle and they mean the same thing. I'm just curious as to why this is showing as a numerical value rather than just have unrestricted file growth ticked when looking at the database properties. Especially when you have ticked it and it just reverts back to the numerical figure. I guess i'm a little uneasy with the fact SQL Server isn't showing what im expecting.

  • Submit it as a bug on Connect. I'd agree with you that it should show that in the GUI.

  • OK I will do that. Cheers for your help.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply