The transaction log for database 'DDE' is full due to 'ACTIVE_TRANSACTION'

In addition to Rahul's answer, there are two possible reasons for the failure with ACTIVE_TRANSACTION:

1. There is a transaction that has been left uncommitted somewhere, maybe in a query window in SSMS. And to this end you can use DBCC OPENTRAN.
2. It is the very stored procedure that you are running that is filling up the log.

Hi @San

The 'ACTIVE_TRANSACTION' part explains that there is an active transaction in the database and because of this, the transaction log file for the database cannot be truncated. To resolve this issue, need to find the active transaction and you may need to stop the activity

You can execute below command to find the active transaction.

use DDE

go

dbcc opentran()

Here are the 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:

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

Please find detailed Microsoft documentation on "Troubleshoot a Full Transaction Log (SQL Server Error 9002)" below-

https://learn.microsoft.com/en-us/sql/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002?view=sql-server-ver16

Thank you!