Platform Deployment Guide › Data Warehouse › Job Configuration Parameters › Fact_Expiry_Age_Months

Fact_Expiry_Age_Months

There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.

Syntax

Set this parameter to n, where n specifies the maximum age in months for events in the data warehouse. The age is measured by the event timestamp and corresponds to the date and time when the event was captured by CA DLP.

SQL Server

@Fact_Expiry_Age_Months=n

Oracle

Fact_Expiry_Age_Months=>n

Examples

For example, if n is 6 and the job runs on 16 December 02:00 AM, all events older than 16 June 02:00 AM are purged from the data warehouse:

@Fact_Expiry_Age_Months=6
Fact_Expiry_Age_Months=>6

Note: There are two main reasons for regularly purging the Data Warehouse:There are two main reasons for regularly purging the data warehouse:

• Purges prevent excessive DBMS storage. Data warehouse tables can grow very quickly, so regular purges prevent them from consuming excessive DBMS storage.

Purges prevent drilldown failures in the iConsole dashboard. The dashboard allows users to drill down into metrics and charts to see the actual underlying incidents. However, drilldown may fail if the main event tables in your CMS database (Wgn3Event and so on) have been purged but the data warehouse tables have not. For example, a pie chart slice could potentially include individual incidents that are no longer present in the CMS database. To avoid this problem, ensure that you purge the data warehouse before purging the corresponding records in your CMS event tables.

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