Zusammenfassung der Ressource
Transaction Control Transformation
- active
- connected
- lets you control
commit and roll
back
transactions
based on a set
of rows that
pass through
- A
transaction
is the set of
rows bound
by commit
or roll back
rows.
- within a mapping:
transformation. Based on the
return value of the expression,
you can choose to commit, roll
back, or continue without any
transaction changes
- If you have a flat file target you
can generate an output file each
time the Integration Service starts
a new transaction. You can
dynamically name each target flat
file.
- targets include
XML, relational,
MQSeries
- Properties Tab
- Transaction
control
expression
- expression
uses the IIF
function to
test each
row
against the
condition
- built-in variables
- TC_CONTINUE_TRANSACTION. The Integration
Service does not perform any transaction
change for this row. This is the default value of
the expression.
- TC_CONTINUE_TRANSACTION. The
Integration Service does not perform
any transaction change for this row.
This is the default value of the
expression.
- TC_COMMIT_AFTER. The
Integration Service writes the
current row to the target,
commits the transaction, and
begins a new transaction. The
current row is in the committed
transaction.
- TC_ROLLBACK_BEFORE. The
Integration Service rolls back the
current transaction, begins a new
transaction, and writes the
current row to the target. The
current row is in the new
transaction.
- TC_ROLLBACK_BEFORE.
The Integration Service
rolls back the current
transaction, begins a new
transaction, and writes the
current row to the target.
The current row is in the
new transaction.
- transaction generators. They define and
redefine transaction boundaries in a mapping.
They drop any incoming transaction boundary
from an upstream active source or transaction
generator, and they generate new transaction
boundaries downstream
- becomes ineffective for downstream
transformations or targets if you put a
transformation that drops incoming
transaction boundaries after it
- Aggregator transformation
with the All Input level
transformation scope ¨ Joiner
transformation with the All
Input level transformation
scope ¨ Rank transformation
with the All Input level
transformation scope ¨ Sorter
transformation with the All
Input level transformation
scope ¨ Custom
transformation with the All
Input level transformation
scope ¨ Custom
transformation configured to
generate transactions ¨
Transaction Control
transformation ¨ A multiple
input group transformation,
such as a Custom
transformation, connected to
multiple upstream transaction
control points
- You must connect
each target
instance to a
Transaction
Control
transformation.
- can connect
multiple targets to
a single
Transaction
Control
transformation.
- can connect
only one
effective
Transaction
Control
transformation to
a targe
- 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.
- A Transaction Control transformation may be effective for
one target and ineffective for another target. If each target
is connected to an effective Transaction Control
transformation, the mapping is valid.
- Either all targets or none of the
targets in the mapping should be
connected to an effective Transaction
Control transformation