Source Based Commits

 
  • The Integration Service commits data to the target based on the number of rows from some active sources in a target load order group.
  • When the Integration Service runs a source-based commit session, it identifies commit source for each pipeline in the mapping.
  • The Integration Service writes the name of the transformation used for source-based commit intervals into the session log:
  • The Integration Service might commit less rows to the target than the number of rows produced by the active source.
  • The number of rows held in the writer buffers does not affect the commit point for a source-based commit session.
  • Source-based commit may slow session performance if the session uses a one-to-one mapping.
  • If the targets are in the same transaction control unit, the Integration Service commits data to the targets at the same time.
  • If the targets are in different transaction control units, the Integration Service performs the commit when each target receives the commit row.
  • A one-to-one mapping is a mapping that moves data from a Source Qualifier, XML Source Qualifier, or Application Source Qualifier transformation directly to a target.
Determining the Commit Source
 

  • A mapping can have one or more target load order groups, and a target load order group can have one or more active sources that generate commits.
  • The Integration Service uses the commits generated by the active source that is closest to the target definition. This is known as the commit source.
  • The Integration Service generates commits at all source qualifiers and transformations that do not propagate transaction boundaries.
  • In single commit source – only one active source generate the commits – which can be either a source qualifier or transformation (that do not propagate transaction boundaries) that is closest to the target definition.
  • In multiple commit source – More than one active source generate the commits – which can be either a source qualifier or transformation (with scope All Input) that is closest to the target definition.
  • If the Integration Service identifies a target in the target load order group that does not receive commits from an active source that generates commits, it reverts to target-based commit for that target only.
  • An XML Source Qualifier transformation does not generate commits when you connect multiple output groups downstream. In this case it will switch to target based commit.
  • You put a commit source between the XML Source Qualifier transformation and the target. The Integration Service uses source-based commit for the target because it receives commits from the commit source. The active source is the commit source for the target.
  • You do not put a commit source between the XML Source Qualifier transformation and the target. The Integration Service uses target-based commit for the target because it receives no commits.

About the Author: kvt

Leave a Reply

Your email address will not be published. Required fields are marked *