Managing Database Growth

As records are created and updated within SAS MDM, the database continues to grow. Much of the growth is due to retired records, information that has been retained in the hub for historical purposes only. Depending on the needs of your organization, the retired records can be removed by transferring the data to offline storage or deleted entirely.
SAS MDM provides a sample job named mdm_archive_<entity_type>.djf that is suitable for customization. This job is not accessible through SAS MDM. You must run it manually. It is used to generate archive files for a specific entity type. The job finds expired records (including audit and entity records), generates files with those records, and removes them from the hub.
Note: Archiving data can result in extensive changes in the hub and might cause performance issues for other users. If possible, restrict archival activity to periods when the hub can be taken offline for maintenance. Alternatively, run archiving frequently enough that the overall operation is quick, or modify the archival jobs to process subsets of the hub.
Last updated: April 19, 2017