Purging a large amount of data

If you have excessive data that you want to purge, or if you have never purged and have waited too long to start, you must reduce the data gradually. Deleting a large amount of data at once will take a very long time and might stall other processes on your system. By deleting smaller sets of data, you will minimize the impact of the purge on your system.

Having a large amount of data can cause your system to process slower. Some purge settings allow you to retain 3650 days of data, and some of those settings have a default of 3000 days. This can cause your database to accumulate a large amount of historical data that you may want to purge.

To reduce data in your database:

 

Step

Example: You have 10 years of bookings in your database, but you want to keep only 3 years of data.

1.

Set the purge settings high. Reduce the number of days by 10%.

The setting ARGOPURGE032 was 3650 days (10 years). In this example, reduce the data one year at a time. Set the new value to 3285 (9 years).

2.

Reduce the value for the setting ARGOPURGE002 (PURGE_MAX_SIZE_IN_RETURN_QUERY) (on page 1) to a smaller number such as 500.

Set ARGOPURGE002 to 500.

3.

Run the Database Purge/Archive background job. The purge background job runs continuously according to the background job schedule.

 

4.

In the Monitor Archive/Purge view, when the Last Purged value is below the Max Result Size, change the purge setting.

Set ARGOPURGE032 to 2920 (8 years).

5.

Run the purge background job.

 

6.

When the Last Purged value is below the Max Result Size, change the purge setting.

Set ARGOPURGE032 to 2555 (7 years).

7.

Run the purge. background job.

 

8.

Repeat this process until you reach the desired setting.

Repeat until ARGOPURGE032 is 1095 (3 years).

9.

If the system does not have memory issues, increase ARGOPURGE002 (PURGE_MAX_SIZE_IN_RETURN_QUERY).

Set ARGOPURGE002  to 1000.