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

Sequence Generator Transformation

Sequence Generator Transformation

The following table shows the pushdown types for each database to which you can push the Sequence Generator transformation:
Database
Pushdown Type
Greenplum
Not supported
IBM DB2
Source-side, Target-side, Full
Microsoft SQL Server
Not supported
Netezza
Not supported
Oracle
Source-side, Target-side, Full
PostgreSQL
Not supported
Sybase
Not supported
Teradata
Not supported
ODBC
Not supported
Microsoft Azure SQL Data Warehouse
Not supported
The Integration Service processes the Sequence Generator transformation if any of the following conditions are true:
  • The transformation is reusable.
  • The transformation is connected to multiple targets.
  • The transformation connects the CURRVAL port.
  • The transformation provides sequence values to a transformation downstream from a Source Qualifier transformation that is configured to select distinct rows.
  • The Integration Service cannot push all of the logic for the Sequence Generator transformation to the database. For example, a Sequence Generator transformation creates sequence values that are supplied to two branches of a pipeline. When you configure pushdown optimization, the database can create sequence values for only one pipeline branch. When the Integration Service cannot push all of the Sequence Generator logic to the database, the following message appears:
    Pushdown optimization stops at the transformation <transformation name> because the upstream Sequence Generator <Sequence Generator transformation name> cannot be pushed entirely to the database.
  • The pipeline branches before the Sequence Generator transformation and then joins back together after the Sequence Generator transformation.
  • The pipeline branches after the Sequence Generator transformation and does not join back together.
  • A sequence value passes through an Aggregator, a Filter, a Joiner, a Sorter, or a Union transformation.
  • The database where the sequence object is created must be the active database or of the same database type as the active database.
The Integration Service processes a transformation downstream from the Sequence Generator transformation if it uses the NEXTVAL port of the Sequence Generator transformation in CASE expressions and is configured for pushdown optimization to IBM DB2.


Updated June 25, 2020