AX2566

Scheduler task: Purge System Data

The Purge System Data task is intended to clean up old data in your system, to help keep your system running efficiently.

NOTE: Scheduler automatically creates a system job for this task (System.SystemDataPurge), which administrators can edit as needed.

This task purges the following data when it is run:

  • Scheduler job result history
  • Scheduler and system email notifications
  • System temp table data
  • Audit history
  • Alerts

For each category of data, you can specify a number of days of data to keep when the task is run. All results older than the specified number of days will be deleted. Note that 0 days means that no data is purged for that category.

Section Item Description
Scheduler Results Number of days to keep result history

The number of days of job result history to keep when the task is run. By default, this is set to 15 days.

SMTP Messages

Number of days to keep delivered messages and attachment data

The number of days of delivered message data to keep when the task is run. By default, this is set to 15 days.

Temporary Tables

Number of days to keep temp table data

The number of days of temp table data to keep when the task is run. By default, this is set to 15 days.

Audit History

Number of days to keep system history

The number of days of system audit history to keep when the task is run. By default, this is set to 15 days.

"System history" encompasses all audit data—including prior document versions and deleted documents—except table audit data.

Table History

Number of days to keep table history

The number of days of table audit history to keep when the task is run. By default, this is set to 15 days.

Table audit data is tracked for tables where Audited is set to True.

Alerts

Number of days to keep alerts

The number of days of alerts to keep when the task is run. By default, this is set to 60 days.

Job variables can be used in all of these settings.

Each purge routine in the task is limited to purging a specific number of rows at a time (50000). If the number of rows to be purged exceeds this limit, then the excess data is retained until the next time the task is run. If you notice data in the database that you expected to be purged, most likely the amount of data to be purged exceeded the limit, and the data will be purged next time the task is run.

Other purged data

This task also cleans up the following items in your system:

  • Deleted columns. When a column is deleted from a table in Axiom Software, the column is immediately deleted from the associated view (which prevents it from being accessed in the system), but it remains in the base table. This task finishes the process of removing obsolete columns from the base tables.

  • Orphaned user folders. If the system contains any user folders that do not match up with existing users, these folders are deleted. Although user folders are deleted when a user is deleted from security, orphaned user folders can result from other processes, such as migrating a system between different management databases.

These items are not associated with any specific task settings; the delete process is performed whenever the task is executed.