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

Optimize the Source Database for Partitioning

Optimize the Source Database for Partitioning

To achieve optimal performance when using multiple threads to read from a DB2 for LUW or an Oracle source database, verify that the source table is partitioned and is configured to accept parallel queries.
To optimize the source database for partitioning, perform the following tasks:
Add database partitions to the source.
Add database partitions to the relational source to increase the speed of the Data Integration Service query that reads the source. If the source does not have database partitions, the Data Integration Service uses one thread to read from the source.
Enable parallel queries.
Relational databases might have options that enable parallel queries to the database. Refer to the database documentation for these options. If these options are not enabled, the Data Integration Service runs multiple partition SELECT statements serially.
Separate data into different tablespaces.
Each database provides an option to separate the data into different tablespaces. Each tablespace can refer to a unique file system, which prevents any I/O contention across partitions.
Increase the maximum number of sessions allowed to the database.
The Data Integration Service creates a separate connection to the source database for each partition. Increase the maximum number of allowed sessions so that the database can handle a larger number of concurrent connections.

0 COMMENTS

We’d like to hear from you!