SQL Step

The SQL step is primarily used to execute SQL statements that do not return data, for example, DDL statements. The syntax of the statements depends on the type of the database being used. To execute stored procedures that return values to the process, you must use a DJImport object in a script step. The SQL step does not return data to the process.

Name	Description
Name	Unique name for the step. You can use alphabets, numbers, and special characters such as -, _. . , and #.
Description	Description for the step (optional).
Enabled	Select this option to enable the step for execution. If it is not enabled, then the step on the canvas is greyed-out. This option is useful when troubleshooting a process, especially when there are numerous steps in the process.
Error Handling	Select either of the following: • Abort Process - All of the steps after this one are skipped or the entire process is aborted (depending on how you have the error logging options set) if this step aborts due to an error. • Ignore Error - The rest of the steps in this process are executed even if this step aborts due to an error.
Choose a SQL Session	Select a SQL session. These sessions are displayed in the drop-down list when you add SQL sessions in the Configuration tab. For more information, see Configuring SQL Sessions in Configuring Processes. Note: Multiple SQL steps can use the same SQL session.
SQL Statement	SQL statement to use in the step.
SQL file	Click Browse and specify the SQL script to use in the step. To escape from SQL into a script during a SQL statement to access and manipulate variables, use DJX. See Script Statements.