Deployment Guide › iConsole Standard Searches, Reports and Policies › Dashboard Data Aggregation › Configure the Aggregation › Aggregation Jobs on SQL Server CMSs

Aggregation Jobs on SQL Server CMSs

To configure the aggregation job for SQL Server CMSs, you need to run a database statement to set the required parameters to their new values. You then run a second statement to go live with these values so they are used in the next aggregation.

1. Set the aggregation parameters: In SQL Server Enterprise Manager Studio, run this database statement:

   EXEC rut_dlp_set_aggregation_values @<parameter>[,@<parameter>]
   

   Where @<parameter> defines the new value for an aggregation parameter. Each query can include multiple parameter definitions, separated by commas. If a parameter is not explicitly specified, it retains its current value. The exception is the purge_data parameter, which is implicitly set if you change the aggregation start date or timeslot length.

   The example below resets the aggregation start date to 1 July and the timeslot length to 24 hours:

   EXEC rut_dlp_set_aggregation_values @start_ts='2008-07-01 00:00:00',
   @granularity=1440,@purge_data=1
   

2. Go live with the new parameters: After running the previous statement, the Output pane displays confirmation details of the new parameters plus the following 'go live' statement:

   EXEC rut_dlp_set_new_values_live <n>
   

   Where <n> uniquely identifies the new set of aggregation parameters. This number is not specified here because it can vary due to various factors.

   You now need to run this go live statement (we recommend you simply copy it from the Output pane into the query pane). This ensures that the next time the aggregation process runs, it will use the new parameter values defined in step 1.

3. Set the aggregation frequency: This step is optional. By default, aggregations run every hour. But if required, you can change the aggregation frequency.

More information:

Aggregation Parameters

Change the Aggregation Frequency