SQL Server transaction log full

Microsoft Troubleshooting Guide

Common reasons for a full transaction log：
The appropriate response to a full transaction log depends on what conditions caused the log to fill. Common causes include:

• Log not being truncated
• Disk volume is full
• Log size is set to a fixed maximum value or autogrow is disabled
• Replication or availability group synchronization that is unable to complete

• check the log disk usage and what action may casued logs unhealthy grow

# check log size
BCC SQLPERF(LOGSPACE)
GO
# check what kind of action casued log unhealthy grow
SELECT name, recovery_model_desc, log_reuse_wait,log_reuse_wait_desc FROM sys.databases
GO

• The following set of T-SQL commands will help you identify if a database transaction log is not truncated and the reason for it. The following script will also recommend steps to resolve the issue:
  • https://docs.microsoft.com/en-us/sql/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002?view=sql-server-ver16
  • https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-databases-transact-sql?view=sql-server-ver16