Log backup on secondary replica fails with error 35296 when the replica sits in the secondary availability group of a distributed availability group. A client hit it on the fourth node of their topology. It is by design, so the backup has to run on a replica that talks to the global primary.
Performance Condition Alerts: Warnings Before a Log File Fills
Build performance condition alerts for log usage, tempdb free space, and blocking, with sensible delays and an operator response.
SQL SERVER – Getting Started with Accelerated Database Recovery – Instant Rollback
Killing a long transaction used to mean a rollback that took forever. SQL Server 2019 fixes that with Accelerated Database Recovery and its instant rollback.
WRITELOG Waits: Finding What Slows Transaction Log Writes
Diagnose WRITELOG waits with log-file latency, commit patterns, and measured choices for batching, storage, and durability.
How to Move Log File or MDF File in SQL Server? – Interview Question of the Week #208
Question: How to Move Log File or MDF File in SQL Server? Here are the steps I use to move a busy LDF or MDF file to a quieter drive.
SQL SERVER – Cannot Shrink Log File 2 (SQLAuthorityDB_log) Because the Logical Log File Located at the End of the File is in Use
Diagnose a cannot shrink log file message with read-only SQL, active VLF checks and log reuse waits. Keep backup protection and size for the workload.
Only Two VLFs: Cannot Shrink the Log File Any Further
A log file with only two VLFs cannot shrink any further, and DBCC SHRINKFILE tells you so. The message says the number of logical log files cannot be fewer than 2. Here is the script that reproduces it and the DBCC LOGINFO output that explains it.