Rules and Guidelines for Working with Transaction Control
Rules and Guidelines for Working with Transaction Control
Consider the following rules and guidelines when you work with transaction control:
Transformations with Transaction transformation scope must receive data from a single transaction control point.
The Integration Service uses the transaction boundaries defined by the first upstream transaction control point for transformations with Transaction transformation scope.
Transaction generators can be effective or ineffective for a target. The Integration Service uses the transaction generated by an effective transaction generator when it loads data to a target.
The Workflow Manager prevents you from using incremental aggregation in a session with an Aggregator transformation with Transaction transformation scope.
Transformations with All Input transformation scope cause a transaction generator to become ineffective for a target in a user-defined commit session.
The Integration Service resets any cache at the beginning of each transaction for Aggregator, Joiner, Rank, and Sorter transformations with Transaction transformation scope.
You can choose the Transaction transformation scope for Joiner transformations when you use sorted input.
When you add a partition point at a transformation with Transaction transformation scope, the Workflow Manager uses the pass-through partition type by default. You cannot change the partition type.