Post reply

Virtual Log files and determining the right growth size estimate of Tlog files.

  • October 14, 2015 at 10:47 am

    #321453

    Hello Experts

    Can you please suggest me a good starting point to understand for a specific db, how many max VLFs are good to have so that it does not cause long startup or backup times?

    Also, I need some calculation so that I can identify a best growth parameter I will setup for each database ?

    I'm seeing the below msg in errorlog and curious to know the changes (right sizing/growth) to be done? As of now 100 MB of log file growth value is set (refer: https://msdn.microsoft.com/en-us/library/bb743398(v=bts.10).aspx)

    Database BizTalkMsgBoxDb has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.

    Thanks.

  • October 14, 2015 at 2:48 pm

    #1833333

    Read both the blog posts below. It's everything you need to know about VLFs.

    http://www.sqlskills.com/blogs/kimberly/8-steps-to-better-transaction-log-throughput/[/url]

    http://www.sqlskills.com/blogs/kimberly/transaction-log-vlfs-too-many-or-too-few/[/url]

  • October 15, 2015 at 12:25 pm

    #1833587

    Pretty useful links- thanks

    Thanks.

  • October 15, 2015 at 8:36 pm

    #1833655

    I have another related question. I found that in bizmsgbox db the VLF count is 500+ and the db log file growth parameter is set as 100 MB. Question is, can that not create a huge tlog file? And do I not needs to shrink the files?

    Bottomline is, what are the specific pitfalls of using a static 100 MB log file growth to all BIZ databases?

    Please suggest

    Thanks.

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

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