Table of Contents

Search

  1. Preface
  2. Introduction to ODBC Connector
  3. Connections for ODBC
  4. Synchronization tasks with ODBC Connector
  5. Mappings and mapping tasks with ODBC Connector
  6. SQL ELT optimization
  7. Data type reference

ODBC Connector

ODBC Connector

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, Full
1
Source, Full
Source, Full
-
-
Source, Full
Source, Full
1
-
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
-
1
You can also configure an unconnected Lookup transformation for Amazon Redshift and Snowflake.
2
To 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.

0 COMMENTS

We’d like to hear from you!