Transaction Log Growth Setting Recommendation

  • Currently, we have a database where the transaction log growth setting is set to grow in 64mb increments. I have read BOL and see that this might be to low; it may take recovery longer because more logical files are created in the transaction log physical file. Other than the default of 10% growth rate, I would like to know what others use for the setting and why. Thank you.

    Regards,

    Mark Yelton

  • Mark

    I usually set the log size to what I think will be the maximum needed and then don't let it grow.  I create a job that dumps it when it gets to 80% full.  If the job runs too often, or if certain large transactions fill the log before it can be truncated, then I will expand the log manually.

    Hope that helps

    John

Viewing 2 posts - 1 through 1 (of 1 total)

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