Table of Contents

Search

  1. Preface
  2. Performance Tuning Overview
  3. Target Optimization
  4. Source Optimization
  5. Transformation Optimization
  6. Mapping Optimization
  7. Partitioned Mapping Optimization
  8. Run-time Optimization
  9. SQL Data Service Optimization
  10. Web Service Optimization
  11. Connections Optimization
  12. Data Transformation Optimization

Performance Tuning Guide

Performance Tuning Guide

Push-Into Optimization with the SQL Transformation

Push-Into Optimization with the SQL Transformation

With push-into optimization, the Data Integration Service pushes the filter logic from a Filter transformation in the mapping to the query in the SQL transformation.
Use the following rules and guidelines when you enable push-into optimization with the SQL transformation:
  • The transformation SQL query must only contain SELECT statements.
  • The transformation SQL query must be a valid subquery.
  • The filter condition cannot refer to the SQL Error or NumRowsAffected fields.
  • The names of the output ports must match the names of the columns in the SQL SELECT statement. When you reference an output port in a filter condition, the Data Integration Service pushes the corresponding port name to the SQL query. You can add aliases to the SQL if the columns in the query do not match the output port names. For example,
    SELECT mycolname1 AS portname1, mycolname2 AS portname2
    .
  • The transformation cannot have side effects.

0 COMMENTS

We’d like to hear from you!