The Integration Service commits data to the target based on the flush latency and the commit type. You can configure a session to use the following commit types:
When you configure a source-based commit, the Integration Service commits data to the target using a combination of the commit interval and the flush latency interval. The first condition the Integration Service meets triggers the end of the flush latency period. After the flush, the counters are reset.
For example, you set the flush latency to five seconds and the source-based commit interval to 1,000 messages. The Integration Service commits messages to the target either after reading 1,000 messages from the source or after five seconds.
When you configure a target-based commit, the Integration Service ignores the commit interval and commits data to the target based on the flush latency interval.
When writing to targets in a real-time session, the Integration Service processes commits serially and commits data to the target in real time. It does not store data in the DTM buffer memory.