To configure data warehousing jobs on SQL Server CMSs, run a database statement to change job parameters to new values. Then run a second statement to go live with these new values.
In SQL Server Enterprise Manager Studio, run the following database statements.
EXEC rut_dlp_set_aggregation_values @<parameter>[,@<parameter>]
Where @<parameter> defines the new parameter value.
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 Truncate_On_Next_Run parameter, which is implicitly set if you change the No_Older_Than_Date parameter. That is, if you change the maximum age of events in the data warehouse, all existing event data gets purged before the job added new event data into the data warehouse.
Available parameters are described in the following sections.
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 job parameters. This number is not specified here because it varies.
Now run this go live statement (we recommend you simply copy it from the Output pane into the query pane). Running the go live statement ensures that the next time the data warehousing job runs, it uses the new parameter values.
The following example resets the oldest event timestamp to 4 July and the maximum event age to 6 months:
EXEC rut_dlp_set_aggregation_values @No_Older_Than_Date='2011-04-01 06:00:00',@Fact_Expiry_Age_Months=6
|
Copyright © 2012 CA.
All rights reserved.
|
|