SQL Server transaction log full

Find why log space cannot be reused.

The problem

Error 9002 can stop writes when log space runs out. Repeated shrinking or extra disk space may miss the reason active log records cannot be released.

Identify the reuse wait
Review sys.databases.log_reuse_wait_desc, recovery model, used log space, file limits and free disk capacity.
Follow the specific cause
Check log backup continuity, long-running transactions, availability replica progress or replication according to the reported wait.
Restore headroom with a recovery plan
Agree the action with the database owner. Preserve the intended recovery model and backup chain while addressing capacity or delayed truncation.
Prevent repeat incidents
Size the log for the workload, review growth settings and backup cadence, and monitor the original reuse wait.

Writes recover and log usage remains stable through the next workload cycle.

Log truncation and file shrinking are different operations. Shrinking alone does not resolve a full active log.