Table of Contents

Search

  1. Preface
  2. Workflow Manager
  3. Workflows and Worklets
  4. Sessions
  5. Session Configuration Object
  6. Tasks
  7. Sources
  8. Targets
  9. Connection Objects
  10. Validation
  11. Scheduling and Running Workflows
  12. Sending Email
  13. Workflow Monitor
  14. Workflow Monitor Details
  15. Session and Workflow Logs
  16. Appendix A: Session Properties Reference
  17. Appendix B: Workflow Properties Reference

Guidelines for Configuring Environment SQL

Guidelines for Configuring Environment SQL

Consider the following guidelines when creating the SQL statements:
  • You can enter any SQL command that is valid in the database associated with the connection object. The Integration Service does not allow nested comments, even though the database might.
  • When you enter SQL in the SQL Editor, you type the SQL statements.
  • Use a semicolon (;) to separate multiple statements.
  • The Integration Service ignores semicolons within /*...*/.
  • If you need to use a semicolon outside of comments, you can escape it with a backslash (\).
  • You can use parameters and variables in the environment SQL. Use any parameter or variable type that you can define in the parameter file. You can enter a parameter or variable within the SQL statement, or you can use a parameter or variable as the environment SQL. For example, you can use a session parameter, $ParamMyEnvSQL, as the connection or transaction environment SQL, and set $ParamMyEnvSQL to the SQL statement in a parameter file.
  • You can configure the table owner name using sqlid in the connection environment SQL for a DB2 connection. However, the table owner name in the target instance overrides the SET sqlid statement in environment SQL. To use the table owner name specified in the SET sqlid statement, do not enter a name in the target name prefix.