Previous Topic: Change the Job ParametersNext Topic: Configure Jobs on Oracle CMSs


Configure Jobs on SQL Server CMSs

To configure data warehousing jobs on SQL Server CMSs, run a database statement to change job parameters to new values.

Syntax

In SQL Server Enterprise Manager Studio, run the following database statement:

EXEC WgnDW_Configure_DW @<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.

Example

In the following example, events older than 12 months are purged from the data warehouse each time a job runs. The job also only copies events captured since the start of 2012 into the data warehouse.

EXEC WgnDW_Configure_DW 
  @Fact_Expiry_Age_Months=12,
  @No_Older_Than_Date='2012-01-01 00:01:00'

The following example enables the Event Participant Fact table and schedules data warehousing jobs to run at 1am for two hours. Events older than 36 months are purged from the data warehouse each time a job runs, and the job also only copies events captured since the start of 2012 into the data warehouse.

EXEC WgnDW_Configure_DW 
  @Is_EP_Fact_Enabled=1,
  @Offpeak_Run_Starttime_Hour=1,
  @Offpeak_Run_Timeout_Mins=120,
  @Fact_Expiry_Age_Months=36,
  @No_Older_Than_Date='2012-01-01 00:01:00' 

More information:

Change the Job Frequency on SQL Server CMSs

Job Configuration Parameters