9002 SQL Origin: Data OSI layer 7 · Application Last updated 18 Nov 2026

SQL Server Error 9002: The transaction log for database is full

The log file can't grow, so writes stop until space is freed.

Exact message you may see 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
Seen on: SQL Server Windows

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

  1. SELECT log_reuse_wait_desc FROM sys.databases
  2. Back up the log: BACKUP LOG db TO DISK=...
  3. Commit/kill the old transaction and free disk

Detailed fix by platform

SQL

  1. SELECT name, recovery_model_desc, log_reuse_wait_desc FROM sys.databases;

How to diagnose

  1. log_reuse_wait — Which?
  2. Log backups — Running?
  3. 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:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

1105 — SQL Server Error 1105: Could not allocate space for object in database because the PRIMARY filegroup is full (SQL)11051222 — SQL Server Msg 1222: Lock request time out period exceeded (SQL)1222209 — SQL Server Msg 209: Ambiguous column name (SQL)2094060 — SQL Server Error 4060: Cannot open database requested by the login. The login failed (SQL)40605123 — SQL Server Msg 5123: CREATE FILE encountered operating system error 5 (Access is denied) while attempting to open the physical file (SQL)5123515 — SQL Server Msg 515: Cannot insert the value NULL into column 'X', table 'Y'; column does not allow nulls (SQL)515701 — SQL Server Msg 701: There is insufficient system memory in resource pool to run this query (SQL)701database or disk is full — SQLite: database or disk is full (SQLITE_FULL) (SQL)database or disk is f…9002

Explore the map of this error Full error map →

🧠 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.