Purge and Retain Data in the Database

You can view the quiesced, unquiesced, and warning thresholds for your database and the percentage of the database that has been used. If you have the Administrator role, you can also set values for the quiesced threshold, unquiesced threshold, warning threshold, and retention times for successful and faulted instances. You can also perform both automatic and ad-hoc purges of the database.

  1. In the navigation pane, click Integrations, then click the < sign next to Designer.
  2. Click Settings > Database.
    The Database Configuration page is displayed.
    Description of database_status.png follows
    Description of the illustration database_status.png
  3. View the current database space usage, the quiesced and unquiesced mode thresholds, and your proximity to the database notification warning threshold (the threshold at which you can receive a notification alert email).
  4. Update threshold values as appropriate, then click Save to activate your updates.
    Field Description
    Quiesced Mode Threshold Click the appropriate up or down arrow to modify the threshold mode value. Runtime operations are shut down and the database enters quiesced mode when this space usage threshold value is reached.
    Un-Quiesce Threshold Click the appropriate up or down arrow to modify the threshold mode value. Runtime operations resume automatically and the database enters unquiesced mode when this space usage threshold value is reached.
    Warning Threshold Click the appropriate up or down arrow to modify the warning threshold. You are notified when this space usage threshold is reached. The warning threshold value must be less than the quiesced mode threshold value and greater than the unquiesced threshold value. See Send Service Failure Alerts, System Status Reports, and Integration Error Reports by Notification Emails.

    Automatic purging also begins when this threshold is reached. You configure automatic purging on the Auto Purge tab of this page.

  5. Click the Nightly Purge tab.
    You can purge instance data of successful and faulted integration instances that have been inactive over a specified period of time and reclaim the database space. Every midnight, the runtime data older than this retention period is purged. These settings take effect when you click Save.
    1. Specify the retention period for purging successful and faulted instances from the system. You can choose to keep the faulted instances data around longer to attempt fault recoveries. Every midnight, runtime data older than the retention periods is purged. This setting goes into effect when you click Save. The Time Unit list enables you to select Days (default is three) or Hours (default is three) for the purge period (in case you need to revert to the defaults by clicking Revert).
    2. Click Purge Now in the top right corner of the page to invoke a dialog to manually perform an ad-hoc purge of the database. This button is available on all three tabs. The next nightly purge still runs as scheduled.
    3. Specify how long to keep the successful and faulted instance data. For example, if your usage is very high, you may choose to purge all successful instances within one hour of completion. Instance data older than the retention values specified is purged immediately when you click Purge Now.
  6. Click the Auto Purge tab.
    1. Click Auto Purge Enabled to automatically purge the database without reclaiming database space when the Warning Threshold value you specified on the Database Space tab is reached. An automatic purge and a reclaim of database space also occurs when the Quiesced Mode Threshold value is reached.
    2. Specify the retention period values for purging successful and faulted instances from the system or click Match nightly purge settings to use the same purge settings as are used for the nightly purge.
    3. Click Save. When the Warning Threshold value you specified on the Database Space tab is reached, an automatic purge occurs.