Abstract:

The transaction log is one of the most critical, yet often misunderstood components of SQL Server. From out of control log growth to very long startup times, problems with the transaction log can cause a lot of pain. In this session, we’ll look at how the transaction log works and how to optimize it’s performance. You’ll learn how to determine the right settings for maximum throughput, and what to do when things get out of control.

Bio - A little about David:

https://dmmaxwell.wordpress.com/about/

My name’s David. I’m a Production Support DBA in Columbus, OH. While I know enough Integration Services or Reporting Services to get around, and I can spell “Analysis Services”, I think the database engine is really where it’s at. I like learning and taking stuff apart to see how it works. This blog is geared solely towards SQL Server, though I occasionally write on other topics elsewhere. If you’re actually interested in what I have to say, or in what I’m up to, feel free to comment on any of my posts, or follow me on Twitter (https://twitter.com/dmmaxwell), and send me questions there.

Thanks for reading,

-David

IndyData

IndyDATA - Microsoft Data Platform User Group

Career & Business

Database Professionals

SQL Server

Business Intelligence

SQL Integration Services

SQL Azure

Advanced SQL Server

Turbo-Charged Transaction Logs w/David Maxwell (@dmmaxwell)

Apparatus 

Share

IndyDATA - Microsoft Data Platform User Group

Turbo-Charged Transaction Logs w/David Maxwell (@dmmaxwell)

IndyDATA - Microsoft Data Platform User Group

Details

Members are also interested in