Purging soft-deleted data to optimize CMDB performance

The Normalization Engine and the Reconciliation Engine enable you to normalize CIs across data sets and then reconcile the duplicate CIs into a final production data set. Besides this, it is equally important to regularly purge the soft-deleted data by using Reconciliation. This helps eliminate CIs that are no longer required in your environment.

Use a Purge activity to physically delete only instances that have been marked as deleted, or soft-deleted. You can optionally further restrict the instances to be purged by using a Qualification Set.

Best practice
If you are purging data from data sets that also serve as source data sets in a Merge activity, you can choose to only delete instances that have also been soft deleted in the target data set. This helps prevent "orphan" instances in the target data set that would never get marked as deleted because no source ever merges with them.

To ensure that users have a chance to review soft-deleted records, we recommend that you make Purge activities part of a standalone job that is executed manually or by workflow events.

To create a Purge reconciliation activity

  1. From CMDB Portal, select Jobs > Manage Reconciliation.
  2. Click Create Job and enter a job name.
  3. Select the appropriate settings for the job.
    To view the details of every setting, hover the cursor over each setting.
  4. Click Add Activity > Purge and perform the following steps:
    The referenced document [confluencePage:page:ac221.Standard reconciliation jobs] was not found.
  5. (Optional) Select a schedule for the job run frequency.
  6. Click Save.
  7. (Optional) To run the job immediately, open the job from All Job Run Activities and click Start Job.

Important

  • For a reconciliation job, if you clear the Disable Progress Bar on UI During Job Execution check box, the number of CIs purged by the reconciliation engine is displayed while the job is running. If you select the check box, the progress bar is not displayed while the job is running, resulting in faster job execution.
  • A strong relationship, as defined in Common Data Model, can be purged safely without causing any data integrity issues.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*