Does This Transaction Log Make My Database Look Fat?

SQL Server

Face it; your database doesn’t get much exercise. It spends its day sitting on the same old server in the same old rack eating garbage all day long. Sure once in a while it may go for a spin, but SSDs are chipping away at that. They may hop around in a VM farm, but for the most part they sit there lazily wasting away the day. What goes into the log? What settings affect the size of the log and what can you do to keep it lean? Join Tim in this 30-minute video to find out:

People who liked this also liked our library of free SQL Server videos.

Previous Post
Automated Tiered Storage for Databases
Next Post
SQL Server in EC2

5 Comments. Leave new

  • Hi,

    I was interested in attending the index seminar, but will be out of the country and not able to view the webcast on the date specified. Will you be posting a review of the webcast on your blog?


  • 2 things:

    1. this video didn’t get posted on the free training page (i don’t think the EC2 video did either)

    2. one reason mentioned to not let log files grow by percent is because the vlfs will have different sizes and cause issues. lets say you shink the log file after doing a tlog backup and set it to grow at a set pace. after the shrink operation will all of the vlf’s be the same size? if not, is this something that we should continue to worry about?

  • Brent,
    Awesome article. I knew most of the information but a refresher is always nice. Anyhow you briefly mentioned that when you see a transaction log suddenly bload exponentially that you use the SQL DMO to look inside the vlf’s to understand why it happened. Can you explain briefly how I could go about tracing a sudden gigantic growth that a log file has in full integrity after the query has already run (or crashed)?


Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.