PowerCenter
- PowerCenter 10.5.1
- All Products
Setting
| Description
|
---|---|
Stored Procedure Name | Name of the stored procedure in the database. The Integration Service uses this text to call the stored procedure if the name of the transformation is different than the actual stored procedure name in the database. Leave this field blank if the transformation name matches the stored procedure name. When using the Import Stored Procedure feature, this name matches the stored procedure. |
Connection Information | Specifies the database containing the stored procedure. You can define the database in the mapping, session, or parameter file:
By default, the Designer specifies $Target for Normal stored procedure types. For source pre- and post-load, the Designer specifies $Source. For target pre- and post-load, the Designer specifies $Target. You can override these values in the session properties. |
Call Text | Text used to call the stored procedure. Only used when the Stored Procedure Type is not Normal. You must include all input parameters passed to the stored procedure within the call text. You can also use a PowerCenter parameter or variable in the call text. Use any parameter or variable type that you can define in the parameter file. |
Stored Procedure Type | Determines when the Integration Service calls the stored procedure. The options include Normal (during the mapping) or pre- or post-load on the source or target database. Default is Normal. |
Tracing Level | Amount of transaction detail reported in the session log file. Use the following tracing levels:
Default is Normal. |
Execution Order | Order in which the Integration Service calls the stored procedure used in the transformation, relative to any other stored procedures in the same mapping. Only used when the Stored Procedure Type is set to anything except Normal and more than one stored procedure exists. |
Subsecond Precision | Specifies the subsecond precision for datetime ports. You can change the precision for databases that have an editable scale for datetime data. You can change subsecond precision for Oracle Timestamp, Informix Datetime, and Teradata Timestamp datatypes. Enter a positive integer value from 0 to 9. Default is 6 (microseconds). |
Output is Repeatable | Indicates whether the transformation generates rows in the same order between session runs. The Integration Service can resume a session from the last checkpoint when the output is repeatable and deterministic. Use the following values:
Default is Based on Input Order. |
Output is Deterministic | Indicates whether the transformation generates consistent output data between session runs. You must enable this property to perform recovery on sessions that use this transformation. Default is disabled. |