Use connection parameters to rerun sessions with different sources, targets, lookup tables, or stored procedures. You create a connection parameter in the session properties of any session. You can reference any connection in a parameter. Name all connection session parameters with the appropriate prefix, followed by any alphanumeric and underscore character.
For example, you run a session that reads from two relational sources. You access one source with a database connection named “Marketing” and the other with a connection named “Sales.” In the session properties, you create a source database connection parameter named $DBConnection_Source. In the parameter file, you define $DBConnection_Source as Marketing and run the session. Set $DBConnection_Source to Sales in the parameter file for the next session run.
If you use a connection parameter to override a connection for a source or target, you can override the connection attributes in the parameter file. You can override connection attributes when you use a non-relational connection parameter for a source or target instance. When you define the connection in the parameter file, the Integration Service searches for specific, user-defined session parameters that define the connection attributes. For example, you create an FTP connection parameter called $FTPConnectionMyFTPConn and define it in the parameter file. The Integration Service searches the parameter file for the following parameters:
