Deployment Guide › iConsole Standard Searches, Reports and Policies › Dashboard Data Aggregation › Aggregation Parameters › Purge Existing Data

Purge Existing Data

SQL Server: @purge_data=1 or 0

Oracle: purge_data=>1 or 0

This determines whether any existing aggregated data is purged from the database. You typically need to purge the aggregated data if you change the timeslot length or the start date. Note also that if you change the aggregation start date, all existing aggregated data is automatically purged, including any aggregated data that was created after the new start date.

If this parameter is set to:

1

All existing aggregated data is purged. Data is re-aggregated from the start date specified by @start_ts or start_ts. If no start date is specified, data is re-aggregated from the start of the current month.

0

Aggregated data for the period before the current aggregation is retained. Any aggregated data for the period after the new start date is deleted. Data is then re-aggregated from the start date specified by @start_ts or start_ts If no start date is specified, data is re-aggregated from the start of the current month. But see the note below.

If the purge parameter is not specified at all, it defaults to 0 (zero). But see the note below.

Note: If you set a new timeslot length (@granularity or granularity), this will force the purge parameter to 1 (even if you have explicitly set the purge parameter to zero). That is, changing the timeslot length will result in all existing aggregated data being purged.