Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Archive data

Log in to subscribe to topics and get notified when content changes.

Archive data

The archive application moves data that is no longer necessary for immediate day-to-day access from primary tables into a set of archive tables.

The longer an instance runs, the more likely it is to accumulate data that is no longer relevant to current business needs. For example, task records from two years ago are typically less relevant than currently active tasks. Old data may eventually cause performance issues by consuming system resources and slowing down queries and reports. If you cannot delete this data because you need it for auditing or for historical purposes, set up an archive rule to archive the data and remove it from immediate access to free up system resources. You can then set up a destroy rule to delete the data after a specified period of time. Destroy rules are available starting with the Helsinki release.

Figure 1. Sample Benefits of Archiving Data

Data archiving supports domain separation. For example, incidents that belong to a domain keep their domain designation even after they are archived.

Note: If you want to archive email, activate the Email retention plugin and use the archive and destruction rules that come with the plugin. Do not use the archive feature to create your own archiving rules on the Email table.