Database Purge; Purging Service Logs

Using the Database Purge to purge Service Logs has been updated as follows:

• The purge was wrapped within one Database Transaction.
• This meant if the purge failed all changes would be rolled back.
• Large databases could take many hours to purge, and having a database transaction active is not good practice.
• Now, each group of Service Logs, i.e. parent/ children, is in its own database transaction.
• If one Service Log fails to be purged it no longer stops the purge, it continues to the next Service Log.
• The "Activity Log" will now record a count of the failures in addition to the current successful count.

• The option to export Service Logs to an XML file has been removed.
• This would create a huge file with potentially sensitive information.
• It would likely cause an out-of-memory error.
• You can export individual Service Logs via the Service Log form.