Amazon Redshift Connector Best Practices

Amazon Redshift Connector Best Practices

Rules and Guidelines for Using Pushdown Optimization

Rules and Guidelines for Using Pushdown Optimization

The following lists the rules and guidelines for using pushdown optimization with Amazon Redshift:
  • You must select the
    Full Pushdown Optimization
    option for the Amazon Redshift source and target table when you have large amount of data.
  • Do not use unconnected lookups.
  • Do not use parallel lookups for mappings. Instead, create a sequential lookups.
  • Eliminate sorted aggregation and pass-through port in an aggregator.
  • Eliminate variable ports.
  • Always set the
    Allow Temporary View for Pushdown
    property when you use pushdown optimization with updates, multiple tables, custom SQLs, and look-ups.
  • Tune the custom Amazon Redshift SQL for ODBC pushdown optimization using the Amazon Redshift Execution Plan.
  • Filter data using
    WHERE
    clause before configuring the outer joins.
  • Do not use full table scans for a large table.
  • Use staging processing if required.
  • Validate the use of sort keys. You can create a sort key on the columns that are most commonly used in the
    WHERE
    clause.
  • To optimize the queries, ensure that you choose the right columns for the distribution option.
  • If you have a Sequence Generator transformation, do not set the
    Allow Temporary View for Pushdown
    property.

0 COMMENTS

We’d like to hear from you!