Purge or archive data records

How to purge or archive data records depends on the requirements of your corporate data retention policy or local laws. User data includes interactions, incidents, problems, changes, and so on.

A typical purge or archive strategy is to archive and delete all incidents that were closed more than <x> months ago.

Business data (for example, an incident) is stored in many tables: The main information is stored in probsummary records; however, there are clock records, file attachments in the SYSATTACHMENTS dbdict, and relation to interactions, change requests, and problems in the screlation dbdict. Additionally, dbdicts as specified in the Object record may also contain information, for example, for activities and so on.

There are multiple options to implement purging or archiving: the Purge/Archive utility, custom implementation inside Service Manager, and custom implementation by an RDBMS implementation. The Purge/Archive utility allows you to set up data maps to archive records along with all of their related records.

Related topics

Cleanup tasks

Purging and archiving records

Archiving and viewing archived Service Manager data using RDBMS Methods