Defining an SQL step

Use the SQL Step notebook to define a step that passes an SQL statement. From this notebook, you can create, generate, or edit SQL statements.

You cannot change the step in Production mode.

../byb.gif Authorities and privileges

To define a step:

  1. Open the step notebook.

  2. Specify information for your step:

  3. On the SQL Statement page, create an SQL statement:

  4. On the Column Mapping page, map the output columns that result from the SQL statement that you defined on the Parameters page to columns on your target table. On this page, output columns from the Parameters page are referred to as source columns. Source columns are listed on the left side of the page. Target columns from the output table linked to the step are listed on the right side of the page. Use the Column Mapping page to perform the following tasks:

    If the Parameters page produces no output columns, or if this step is not linked to a target table and you have not specified automatic generation of a default table in the Parameters page, you will not be able to use this page to map your columns. Some steps will not allow you to change the column mapping.

  5. On the Processing Options page, in the Population type list, select whether the step appends or replaces data in the target.

  6. In the Agent Site list, select an agent site where you want your step to run. The selections in this list are agent sites that are common to the source tables and the target table.

  7. If you want to have the option to to run your step at any time, select the Run on demand checkbox. Your step must be in test or production mode before you can run it.

  8. Optional: Select the Populate externally check box if the step is populated externally, meaning that it is invoked in some way other than by the Data Warehouse Center. The step does not have to have any other means of running in the Data Warehouse Center in order to change the mode to production.

    If Populate externally is not selected, then the step must either have a schedule, be linked to a transient table that is input to another step, or be started by another program in order to change the mode to production.

  9. In the Retry area, specify how many times you want the step to run again if it needs to be retried and the amount of time that you want to pass before the next run of the step.

  10. In the Return Codes area, select the return code level that you would like to receive if no rows are returned or an SQL warning occurs when your step is run.

  11. In the Incremental commit checkbox and the Every x rows field, specify whether you want the step to perform an incremental commit and, if so, how often you want the commit to occur.

  12. Click OK to save your changes and close the step notebook.

Related information

Moving and transforming data

Population type descriptions

List of steps and step subtypes

Data Warehouse Center concepts