How do I know if my transaction log is full?

What happens if transaction log is full?

When the transaction log becomes full, SQL Server Database Engine issues a 9002 error. The log can fill when the database is online, or in recovery. If the log fills while the database is online, the database remains online but can only be read, not updated.

How do I fix the full transaction log?

Try one of the 4 suggestion below to fix this issue:1Under SQL Server Management Studio set the Maximum File Size under options for Altiris database to Unrestricted File Growth.2Increase the Restricted File Growth (MB) size to a larger value creating space for transaction logs to grow.3Shrink the log files from task.The Transaction Log for database 'DB' is full due to 'LOG_BACKUP'.

How do I clear transaction log database is full?

Truncate the transaction log1Right-click the database and select Properties -> Options.2Set the recovery model to Simple and exit the menu.3Right-click the database again and select Tasks -> Shrink -> Files.4Change the type to Log .5Under Shrink action, select Reorganize pages before releasing unused space and click OK.Truncate and shrink log files in SQL Server - - Rackspace

Why is my transaction log file so big?

Therefore the most common reason I have experienced for a transaction log file to have grown extremely large is because the database is in the FULL recovery model and LOG backups haven't been taken for a long time. * Its important to note that the space within the transaction log is just marked as available again.