Platinum Sponsor

SQL Server Transaction Log Internals and Management

Transaction log is an integral part of your database. Every change that happens is first written into it because SQL Server uses the WAL (write ahead logging) to provide atomicity and durability in a database.

There are many questions (involuntary) DBAs ask themselves like: do I need more than one transaction log, where should I put it, what and how it actually gets logged, what's the proper backup/restore strategy, can i read it, etc...?

In this session we'll try to answer all these questions by doing a dive into the fun world of how transaction logs work and what you have to watch out for in your environments.
Presented by Mladen Prajdić at SQLBits XI
Tags (no tags)
  • Downloads
    Sorry, there are no downloads available for this session.
  • SpeakerBIO
    Mladen_Prajdic.png
    Mladen Prajdić is a SQL Server MVP from Slovenia and a C# and SQL Server developer for over 10 years. He blogs at http://weblogs.sqlteam.com/mladenp. He develops a popular add-in for SSMS, called SSMS Tools Pack (http://www.ssmstoolspack.com/).
    http://weblogs.sqlteam.com/mladenp http://feeds.feedburner.com/mladenp
  • Video
    The video is not available to view online.
  • Session Files Explorer
    The network name cannot be found.