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

Constraints

Constraints

The Data Integration Service can read constraints from relational sources, flat file sources, logical data objects, or virtual tables. A constraint is a conditional expression that the values on a data row must satisfy.
When the Data Integration Service reads constraints, it might drop the rows that do not evaluate to TRUE for the data rows based on the optimization method applied.
Before you set a constraint, you must verify that the source data satisfies the condition set by the constraint.
For example, a source database has an AGE column that appears to have rows with AGE < 70. You can set a constraint with AGE < 70 on the source database. The Data Integration reads records from the source database with the constraint AGE < 70. If the Data Integration Service reads records with AGE >= 70, it might drop the rows with AGE >= 70.
In the database, you can use SQL commands to set constraints on the database environment when you connect to the database. The Data Integration Service runs the connection environment SQL each time it connects to the database.
Use the Developer tool to set constraints on logical data objects, physical data objects, and virtual tables. When you set a constraint, you must enter an expression that evaluates to TRUE for each data row.

0 COMMENTS

We’d like to hear from you!