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.
Capping File Growth So One Query Cannot Fill a Whole Disk
One runaway load can fill a shared drive and take every database down with it. A MAXSIZE cap moves the failure to one database.
Metadata-Only Column Changes: Which ALTER COLUMN Is Instant
Six ALTER statements look equally small, but their log cost is not. Here is how to measure each one before the change window.
Point-in-Time Restore: Getting Back Rows Deleted by Accident
Plan a point-in-time restore after an accidental DELETE, preserve the log chain, recover a separate copy, and return reviewed rows.
Resumable Index Rebuilds: Pausing Maintenance Without Losing Progress
Run a resumable index rebuild with ONLINE and MAX_DURATION, pause and resume it, inspect progress, and weigh edition and log costs.