Set-up Maximum Log File Size growth in SQL 2005

Hello experts,

Please advise waht is the best practice to set-up max file log size growth in SQL 2005. As per the attached screenshot, it is set to 2 TB, my plan is to set it to 2 GB so that log size will not grow beyond 2 GB.

Is this correct?

Please advise.

Thanks and Regards Autogrowth
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

depends on how big your datafile is . if its a huge datafile and you are doing huge updates or inserts or even reindexing, or sorting then 2GBs will fill up quite quickly. i would suggest you set it to grow by 10% and monitor it for a few weeks. If you are satisfied that xGBs is the max file to keep then set it to that.

Anthony PerkinsCommented:
>>Please advise waht is the best practice to set-up max file log size growth in SQL 2005<<
Whatever works for you in your particular case.  Just understand that when you set a max and a query causes the max to be reached, than it will fail as well as all subsequent queries, until the transaction log is backed up (if the Recovery Model is set to Full) or a checkpoint is reached (when the Recovery Model is set to Simple)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Daniel_PLDB Expert/ArchitectCommented:
Please note when log will reach max size value without any intervention (manually resizing or adding additional log file) database will stop.
I suggest changing default percentage grow to value in MB.

Read some advices from Kimberly L. Tripp and Paul S. Randal ;):
Its better to analyze your database growth with 2 TB\unlimited growth option for a week and then set your criteria with this. As others said above, the log growth completely depends upon the transactions happening on the server, so I think this is the correct way. Apart from that the percentage of size growth also matters a lot. Consider it too for configuring your log.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.