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

Sorter Transformation

Sorter Transformation

The following table shows the pushdown types for each database to which you can push the Sorter transformation:
Database
Pushdown Type
Amazon Redshift
Source-side, Full
Greenplum
Source-side, Full
IBM DB2
Source-side, Full
Microsoft SQL Server
Source-side, Full
Netezza
Source-side, Full
Oracle
Source-side, Full
Sybase ASE
Source-side, Full
Teradata
Source-side, Full
Vertica
Source-side, Full
Microsoft Azure SQL Data Warehouse
Not Supported
Use the following rules and guidelines when you configure the Integration Service to push Sorter transformation logic to a database:
  • The Integration Service pushes the Sorter transformation to the database and processes downstream transformations when the Sorter transformation is configured for a distinct sort and is pushed to a Microsoft SQL Server, Sybase, or Teradata database.
  • If a mapping contains multiple, consecutive Sorter transformations and at least one Sorter transformation is configured for a distinct sort, the following results:
    • Pushdown optimization applies the distinct sort to the last Sorter transformation in the chain unless one of the Sorter transformations does not project all output ports.
    • Pushdown optimization applies the distinct sort to the first Sorter transformation that does not project all output ports.
The Integration Service processes the Sorter transformation if any of the following conditions are true:
  • The Sorter transformation is downstream from a Union transformation and the port used as a sort key in the Sorter transformation is not projected from the Union transformation to the Sorter transformation.
  • The Sorter transformation does not project all output ports and it is one of multiple, consecutive Sorter transformations in a mapping.
  • The Sorter transformation does not project all output ports and one of the following statements is true:
    • The Sorter transformation is configured for a distinct sort.
    • The Sorter transformation is immediately preceded by one or more Sorter transformations, one of which is configured for a distinct sort.


Updated June 03, 2019