When the Integration Service processes a Joiner transformation, it can apply transformation logic to all data in a transaction, all incoming data, or one row of data at a time. The Integration Service can drop or preserve transaction boundaries depending on the mapping configuration and the transformation scope. You configure how the Integration Service applies transformation logic and handles transaction boundaries using the transformation scope property.
You configure transformation scope values based on the mapping configuration and whether you want to preserve or drop transaction boundaries.
You can preserve transaction boundaries when you join the following sources:
You join two branches of the same source pipeline.
Use the Transaction transformation scope to preserve transaction boundaries.
You join two sources, and you want to preserve transaction boundaries for the detail source.
Use the Row transformation scope to preserve transaction boundaries in the detail pipeline.
You can drop transaction boundaries when you join the following sources:
You join two sources or two branches and you want to drop transaction boundaries
. Use the All Input transformation scope to apply the transformation logic to all incoming data and drop transaction boundaries for both pipelines.
The following table summarizes how to preserve transaction boundaries using transformation scopes with the Joiner transformation:
Integration Service Behavior
Preserves transaction boundaries in the detail pipeline.
Preserves transaction boundaries when master and detail originate from the same transaction generator. Session fails when master and detail do not originate from the same transaction generator
Drops transaction boundaries.
Sessions fail if you use real-time data with All Input or Transaction transformation scopes.