A
commit interval is the interval at which the server commits data to relational
targets during a session.
Three types of Commit Intervals:
Target based commit.
Source based commit.
User defined Commit.
If you use in Transaction control Transformation that time the commit type is automatically convert to User defined commit.
Default commit interval is Target.
(a)
Target based commit
1. Server commits data based on the no
of target rows and the key constraints on the target table. The commit
point also depends on the buffer block size and the commit interval.
2. During a session, the server
continues to fill the writer buffer, after it reaches the commit interval.
When the buffer block is full, the Informatica server issues a commit
command. As a result, the amount of data committed at the commit point
generally exceeds the commit interval.
3. The server commits data to each
target based on primary –foreign key constraints.
(b)
Source based commit
1. Server commits data based on the
number of source rows. The commit point is the commit interval you
configure in the session properties.
2. During a session, the server commits
data to the target based on the number of rows from an active source in a
single pipeline. The rows are referred to as source rows.
3. A pipeline consists of a source
qualifier and all the transformations and targets that receive data from
source qualifier.
4. Although the Filter, Router and
Update Strategy transformations are active transformations, the server
does not use them as active sources in a source based commit session.
5. When a server runs a session, it
identifies the active source for each pipeline in the mapping. The server
generates a commit row from the active source at every commit interval.
6. When each target in the pipeline
receives the commit rows the server performs the commit.
Subscribe to:
Post Comments (Atom)
Post a Comment