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

Data Age

SQL Server: @data_age=<n>

Oracle: data_age=><n>

Specifies the maximum age (in months) for data in the aggregation tables. These tables contain the aggregated incident data used to generate the dashboard charts and metrics. If you set this parameter, any records older than <n> months are purged from the aggregation tables when an aggregation job next runs. For example, if <n> is 3 and the aggregation job runs on 16 December 02:00 AM, all records older than 16 September 02:00 AM will be purged from the aggregation tables:

@data_age=3

data_age=>3

There are two main reasons for regularly purging the aggregation tables:

• Prevent excessive DBMS storage: The aggregation tables can grow very quickly, so regular purges will prevent them from consuming excessive DBMS storage.
• Support for dashboard drill down: The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drill down may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the aggregation tables have not. For example, in this situation a pie chart slice could potentially include some individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that your aggregation tables are purged before the corresponding records in your main event tables.