Table of Contents

Search

  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  16. Datatype Reference
  17. Configure the Web Browser

Rules and Guidelines for Adding Pre- and Post-Session SQL Commands

Rules and Guidelines for Adding Pre- and Post-Session SQL Commands

Use the following rules and guidelines when you enter pre- and post-session SQL commands in the target instance:
  • Use any command that is valid for the database type. However, the Integration Service does not allow nested comments, even though the database might.
  • You can use parameters and variables in the in the target pre- and post-session SQL commands. For example, you can enter a parameter or variable within the command. Or, you can use a session parameter, $ParamMyCommand, as the SQL command, and set $ParamMyCommand to the SQL statement in a parameter file.
  • Use a semicolon (;) to separate multiple statements. The Integration Service issues a commit after each statement.
  • The Integration Service ignores semicolons within /* ...*/.
  • If you need to use a semicolon outside of comments, you can escape it with a backslash (\).
  • The Designer does not validate the SQL.
You can also enter pre- and post-session SQL commands on the Properties tab of the Source Qualifier transformation.


Updated July 02, 2020