Pigeon Voice Server Database Log Purging - DatasmithSA/Pigeon-Voice-Training GitHub Wiki
Due the considerations mentioned in the Database Log Disk Usage section, it is important to perform regular house cleaning on the Pigeon Voice database. In order to manage the size of the Pigeon database log, the Pigeon Voice Server provides a feature that enables purging (deleting) of the historical log entries from the database automatically in the background.
The Database Log Purge Job is executed daily by the Pigeon Voice Server at a time that can be configured. Once the job has executed its Next Execution Date Time setting is then updated to the following day at the same time i.e. 24 hours later. The number of historical log entries that are kept is determined by the Database Log Entries Days To Keep setting e.g. changing this setting to 10 will keep only log entries for the last 10 days and delete entries older than that when the purge job runs.
As mentioned in the Logging Settings the following settings are relevant to the purging of the database log:
- Enable Database Log Purge Job: Whether or not to purge (delete) historical database log entries that are older than a specific number of days.
- Database Log Purge Job Next Execution Date Time: The date and time that the Database Log Purge Job will execute. N.B. if the value is being updated in the settings file manually, the value of the DatabaseLogPurgeJobNextExecutionDateTimeSerialized setting must be set in the following format: yyyy-MM-ddTHH:mm:ss
- Database Log Entries Days To Keep: The number of days of database log entries to keep i.e. entries older than the specified number of days will be purged (deleted) if the Database Log Purge Job is enabled.
/images/manager/LogPurgeJobSettings.png
When running the Pigeon Voice Server in console mode, The Database Log Purge Job can be seen getting initiated and executing automatically in the background.
/images/manager/LogPurgeJobRunning.png
The activity for the Database Log Purge Job is also logged in both the database and in the Windows Event Log:
