Post reply

Large Transaction Log size

  • March 27, 2012 at 4:10 am

    #258312

    Dear Gurus,

    While configuring the log file sizes, i believe the best practice says to have the log file as 25% the size of the total data files.

    I have a situation where the production database (data file size) is only 6-GB in size where as the log file is 9 GB in size. There is proper log backup scheduled on a daily basis. Most of the Virtual log files are empty.

    Please suggest if there is any performance impact of the large transaction log file like in this case. What's coming to my mind is that since the Transaction log file is large, there will be too many VLFs and the VLF sizes will be large too.

    Will this configuration impact overall database performance in any way?

    Thanks in advance for the inputs.:hehe:

  • March 27, 2012 at 5:12 am

    #1464874

    A large log (and 9GB is far from large) will not impact performance. Lots of VLFs (regardless of log size) can and do affect performance of backups, database recoveries and other things reading the log. See Kimberly Tripp's article on transaction log throughput.

    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

  • March 27, 2012 at 5:36 am

    #1464884

    Thanks Gail. This answers my question.:-)

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

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