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
  26. POWERCENTERHELP

Advanced Workflow Guide

Advanced Workflow Guide

Aggregator Transformation

Aggregator Transformation

The following table shows the pushdown types for each database to which you can push the Aggregator 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
SAP HANA
Source-side, Target-side, Full
Sybase ASE
Source-side, Full
Teradata
Source-side, Full
Vertica
Source-side, Full
The Integration Service processes the Aggregator transformation if any of the following conditions are true:
  • The session and mapping is configured for incremental aggregation.
  • The transformation contains a nested aggregate function.
  • The transformation contains a conditional clause in an aggregate expression.
  • The transformation uses a FIRST(), LAST(), MEDIAN(), or PERCENTILE() function in any port expression.
  • An output port is not an aggregate or a part of the group by port.
  • The transformation is pushed to Microsoft SQL Server, Sybase, or Teradata and is downstream from a Sorter transformation.


Updated July 04, 2018