Incoming data must be sorted by the fields that you use in the transaction condition. Place a Sorter transformation upstream of the Transaction Control transformation or use a sorted data source.

Configuring the transaction control condition to perform frequent commits can affect performance.

If the mapping includes an XML target, and you choose to append or create a new document on commit, the input groups must receive data from the same transaction control point.

Transaction Control transformations that are connected to any target that does not support batch or transaction real-time processing are ineffective for those targets.

You must connect each target instance to a Transaction Control transformation.

You can connect multiple targets to the same Transaction Control transformation.

You can connect only one effective Transaction Control transformation to a target.

You cannot place a Transaction Control transformation in a pipeline branch that starts with a Sequence Generator transformation.

If you use a dynamic Lookup transformation and a Transaction Control transformation in the same mapping, a rolled-back transaction might result in unsynchronized target data.

Either all targets or no targets in the mapping should be connected to an effective Transaction Control transformation.