Data Monitoring / SQL Server Availability & Capacity
SQL Server: Transaction log growth
A database log expands even after routine log backups. Inspect log reuse wait reason, backup history and long transactions.
Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.
Failure scenario
A database log expands even after routine log backups. Confirm the cause before choosing a fix.
Evidence to collect
Inspect log reuse wait reason, backup history and long transactions. Record the time, affected scope and a healthy comparison interval.
Worked diagnostic example
Read-only SQL Server log-reuse evidence; investigate the reported reason before changing anything.
SELECT name, recovery_model_desc, log_reuse_wait_desc
FROM sys.databases;Fix the confirmed cause
Resolve the actual reuse blocker before changing file sizes or backup schedules. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for transaction log growth using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.