SQL Server Error 9002: The transaction log for database is full
The log file can't grow, so writes stop until space is freed.
The transaction log for database is full due to 'LOG_BACKUP'The transaction log for database is full due to 'ACTIVE_TRANSACTION'log_reuse_wait_desc LOG_BACKUP Meaning
Check log_reuse_wait_desc in sys.databases: LOG_BACKUP (take a log backup), ACTIVE_TRANSACTION (end the long transaction), REPLICATION, AVAILABILITY_REPLICA. Switch to SIMPLE recovery only if point-in-time recovery isn't needed, and free disk space.
Common causes
- FULL recovery without log backups
- Long open transaction
- Disk full or log MAXSIZE reached
- Replication/AG holding the log
- Huge bulk operation
⚡ Quick fix
SELECT log_reuse_wait_desc FROM sys.databases- Back up the log:
BACKUP LOG db TO DISK=... - Commit/kill the old transaction and free disk
Detailed fix by platform
SQL
SELECT name, recovery_model_desc, log_reuse_wait_desc FROM sys.databases;
How to diagnose
- log_reuse_wait — Which?
- Log backups — Running?
- Disk — Free?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026