The SQL Server transaction log works like a string of log records, each with an LSN. My simple notes on the basic architecture of transaction logs.
SQL SERVER – Understanding the Basics of Write Ahead Logging (WAL) Protocol
Doing the basics right matters. Here is a simple, story-driven explanation of the Write Ahead Logging (WAL) protocol that keeps SQL Server transactions safe.
Autogrowth Settings: Why 1 MB and 10 Percent Still Hurt
Inspect autogrowth settings across database files, review retained growth events and VLFs, and choose tested fixed-size increments.
SQL SERVER – Script: Knowing Data and Log Files Are On the Same Drive
At GIDS I talked about keeping data and log files on separate drives. Here is a script that shows which databases have data and Log Files on the same drive.
SQL SERVER – Beginning Reading Transaction Log File
What is the SQL Server transaction log, why do we need it and how does it work? A beginner’s first step toward reading transaction log file content.
Delayed Transaction Durability Explained: SQL in Sixty Seconds #074
Delayed transaction durability lets a commit return before its log record reaches the disk. This post explains the idea and the three settings, then measures 10,000 small transactions on SQL Server 2025 and shows the one risk with a log write count. It ends with a simple rule for using it safely.
Example of Delayed Durability: How Much Faster Are Commits?
This example of delayed durability runs 50,000 small transactions on SQL Server 2025 four ways and compares time and log writes. It shows what the database setting and the commit option change, and what you risk.