ODBC Connector > SQL ELT optimization > SQL ELT optimization transformations
  

SQL ELT optimization transformations

When you configure SQL ELT optimization, the Secure Agent tries to push the configured transformation to the database.
The following table shows the supported SQL ELT optimization types for each database to which you can push the transformation:
Transformations
Amazon Redshift
DB2
Google BigQuery
Microsoft Azure SQL Data Warehouse
Netezza
PostgreSQL
Snowflake
Teradata
Aggregator
Source, Full
Full
Source, Full
Full
Source, Full
Source, Full
Source, Full
Source, Full 2
Expression
Source, Full
Full
Source, Full
Full
Source, Full
Source, Full
Source, Full
Source, Full 2
Filter
Source, Full
Source, Full
Source, Full
Full
Source, Full
Source, Full
Source, Full
Source, Full
Joiner
Source, Full
Source, Full
Source, Full
Full
Source, Full
Source, Full
Source, Full
Source, Full
Lookup
Source, Full1
Source, Full
Source, Full
-
-
Source, Full
Source, Full1
-
Sorter
Source, Full
Source, Full
Source, Full
Full
Source, Full
Source, Full
Source, Full
Source, Full
Union
Source, Full
Source, Full
Source, Full
Full
Source, Full
Source, Full
Source, Full
Source, Full
Router
Full
Source, Full
Full
Full
Full
-
Full
Full
Update Strategy
-
Source, Full
Source, Full
-
-
-
-
-
Sequence Generator
-
-
-
-
-
-
Source, Full
-
1You can also configure an unconnected Lookup transformation for Amazon Redshift and Snowflake.
2To enable Expression or Aggregator transformation in a Teradata mapping task, see the "Enabling SQL ELT optimization for Expression and Aggregator transformations" topic in the Teradata Connector guide.