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.
ASK INFAPreview
