Transaction log grows to a large size due to uncommitted insert to SY_LicenceUsages table

Problem

Transaction log grows to a large size due to uncommitted insert to SY_LicenceUsages table - 7.00.175

Solution

This is caused by database backups not being able to truncate the log because an open transaction exists. The open transaction is from the plugin scheduler - it is created upon service start and closed upon service stop.

The solution to this is to re-design the way licences are enforced (i.e. don't rely on an uncommitted transaction to indicate a licence usage). This is a big change with far reaching effects, and not something we are currently in a position to do.

The workaround is to restart the service on a regular basis to allow the transaction log to be truncated until this issue is addressed in a future release.  

Related articles