You are here: EDQ Applications > Director > How To Guides > Purging results

Purging Results

EDQ uses a repository database to store the results and data it generates during processing. All Results data is temporary, in the sense that it can be regenerated using the stored configuration, which is held in a separate database internally.

In order to manage the size of the Results repository database, the results for a given set of staged data (either a snapshot or written staged data), a given process, a given job, or all results for a given project can be purged.

For example, it is possible to purge the results of old projects from the server, while keeping the configuration of the project stored so that its processes can be run again in the future.

Note that the results for a project, process, job, or set of staged data are automatically purged if that project, process, job, or staged data set is deleted. If required, this means that project configurations can be packaged, the package import tested, and then deleted from the server. The configurations can then be restored from the archive at a later date if required.

To purge results for a given snapshot, set of written staged data, process, job, or project:

  1. Right-click on the object in the Project Browser. The purge options are displayed.
  2. Select the appropriate Purge option.

If there is a lot of data to purge, the task details may be visible in the Task Window.

Note:

 

Purging Match Decision data

Match Decision data is not purged along with the rest of the results data. Match Decisions are preserved as part of the audit trail which documents the way in which the output of matching was handled.

If it is necessary to delete Match Decision data, for example, during the development process, the following method should be used:

  1. Open the relevant Match processor.
  2. Click Delete Manual Decisions.
  3. Click OK to permanently delete all the Match Decision data, or Cancel to return to the main screen.

Note:The Match Decisions purge takes place immediately. However, it will not be visible in the Match Results until the Match process is re-run. This final stage of the process updates the relationships to reflect the fact that there are no longer any decisions stored against them.

Oracle ® Enterprise Data Quality Help version 11
Copyright © 2006, 2013, Oracle and/or its affiliates. All rights reserved.