The following tables list the required and optional properties of the SQL Executor component.
Property |
Description |
---|---|
Interface |
Identify the method or driver to use to connect to the data source. |
Host Name |
Identify the data source. The options that appear in the Host Name list depend on the interface you select. |
Execute Script |
Specify the custom SQL script to be executed. |
Property |
Description |
---|---|
User and Password |
Identify an authorized database user and protect the database against unauthorized access. |
Execute Success Script |
Specify the custom SQL to be executed, if the Execute Script runs successfully. |
Execute Error Script |
Specify the custom SQL to be executed, if the Execute Script fails. |
Pre Processing SQL |
Create a script that runs during component initialization. Scripts can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;). |
Post Processing SQL |
Create a script that runs after all components execute. Scripts can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;). |
Database |
Identify the database to use as data source. If you select this option, you must also select an appropriate interface, and in some cases, specify an appropriate user ID and password. |
Schema |
Identify the schema or owner you want to use as data source. The objects that appear are restricted accordingly and new tables are created in the schema you specify. |
Database Options |
Set options that override performance defaults and control the behavior of some transactions. |
Transactional |
All work performed by the SQL Executor component, including pre-SQL and post-SQL, is done in a single database transaction that is committed when the project finishes normally. Select this option to roll back the transaction, if this component encounters an error. See “Job components” and “Enabling transactionality for projects and jobs” for information on the “Propagate Rollback” property. |