Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data

Advanced Workflow Guide

Advanced Workflow Guide

Setting Commit Properties

Setting Commit Properties

When you create a session, you can configure commit properties. The properties you set depend on the type of mapping and the type of commit you want the Integration Service to perform. Configure commit properties in the General Options settings of the Properties tab.
The following table describes the session commit properties that you set in the General Options settings of the Properties tab:
Property
Target-Based
Source-Based
User-Defined
Commit Type
Selected by default if no transaction generator or only ineffective transaction generators are in the mapping.
Choose for source-based commit if no transaction generator or only ineffective transaction generators are in the mapping.
Selected by default if effective transaction generators are in the mapping.
Commit Interval
Default is 10,000.
Default is 10,000.
n/a
Commit on End of File
Commits data at the end of the file. Enabled by default. You cannot disable this option.
Commits data at the end of the file. Clear this option if you want the Integration Service to roll back open transactions.
Commits data at the end of the file. Clear this option if you want the Integration Service to roll back open transactions.
Roll Back Transactions on Errors
If the Integration Service encounters a non-fatal error, you can choose to roll back the transaction at the next commit point.
When the Integration Service encounters a transformation error, it rolls back the transaction if the error occurs after the effective transaction generator for the target.
If the Integration Service encounters a non-fatal error, you can choose to roll back the transaction at the next commit point.
When the Integration Service encounters a transformation error, it rolls back the transaction if the error occurs after the effective transaction generator for the target.
If the Integration Service encounters a non-fatal error, you can choose to roll back the transaction at the next commit point.
When the Integration Service encounters a transformation error, it rolls back the transaction if the error occurs after the effective transaction generator for the target.
When you bulk load to Microsoft SQL Server or Oracle targets, define a large commit interval. Microsoft SQL Server and Oracle start a new bulk load transaction after each commit. Increasing the commit interval reduces the number of bulk load transactions and increases performance.


Updated June 03, 2019