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.