Schedule and Configure Database Purge
Use this wizard panel to set the frequency and at which the purge jobs are to occur.
Field |
Description |
---|---|
Maintenance name |
Specify a unique name for the job to help you distinguish it among others on the Database Maintenance page. By default the name is Recurring purge job -[current date][current time]. Consider using a name that reflects characteristics of the job, such as:
|
Scheduling
Field |
Description |
---|---|
Daily |
Select if you want to run the purge daily. |
Weekly |
Select if you want to run the purge weekly. |
Start date |
Enter the date you want the recurring purge job to start. It must be in the MM/DD/YYYY date format (for example, 05/18/2015), not text such as "May 18, 2015". Click the date icon |
Start time |
Enter the time you want the recurring purge job to start. It must be in the 12-hour time format (for example, 1:00 PM). Click the time icon |
Run every |
Enter the interval that you want the purge to occur. If you selected a frequency of Weekly, also select the days you want the job to run. |
Database settings
Field |
Description |
---|---|
Purge events older than |
Set the minimum age of events (integer representing days) you want the job to purge. Only events older than the specified number are eligible for deletion. For example, if you enter 100 days all events 101 days and older are removed. Default: 90 days. |
Maximum purge duration |
Set the maximum number of minutes that the purge job can run. You may want to limit the purge duration so, for example, it does not coincide with replication or import/export tasks. The purge stops when the minutes set expire and the system finishes the current batch it is purging. Depending on how long it takes your database to purge a batch of a particular size, this can add several minutes to the actual purge duration. Default: 60 minutes. |
Batch size |
Set the number of rows to be included in each batch operation. A single purge operation typically includes multiple batch deletions. Larger batch sizes mean bigger database transactions and more database locks. Default: 2000 rows. |