KBI 312114 – Issue Addressed: The Transaction Log for Database XXXX Is Full Due to ‘LOG_BACKUP’


Argent Omega 2.2A-2307-B or later


Tuesday, 24 October 2023


Argent Omega might encounter SQL error “The transaction log for database XXXXXXXXXX is full due to ‘LOG_BACKUP’”.

This is caused by SQL Server running out of space for transaction logs.

Argent Omega 2.2A-2307-B (Build: 2.2.2210.4) has been enhanced to periodically backup and shrink transaction logs.

This has been enabled on Argent Omega Generator screen (E2). By default, it is not enabled. Argent Omega Generator runs this once every hour.

If Log Backup Device is not specified, Argent Omega service will simply shrink SQL transaction logs without doing backup first.

Technical Background

Since SQL Server 2008 R2, there is no more ‘TRUNCATE_ONLY’ option for query ‘BACKUP LOG’. In order to not let log size growing unchecked, DBA must backup logs frequently. By creating a Backup Device in SQL Server and using it in Argent Omega configuration, Argent Omega service does the backup automatically.

Another option to avoid such SQL error is to change Database Recovery Model from Full to Simple. Though Simple model generates transaction logs too, they are automatically truncated when a checkpoint operation is performed. Simple model is regarded as less safe then Full model. DBA must perform database backup frequently.


Upgrade to Argent Omega 2.2A-2307-B or later.

For further assistance, please contact Argent on Instant Help at