Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Using Sorted Input

Using Sorted Input

When you configure a flat file Lookup transformation for sorted input, the condition columns must be grouped. If the condition columns are not grouped, the Lookup transformation returns incorrect results. For optimal caching performance, sort the condition columns.
For example, a Lookup transformation has the following condition:
OrderID = OrderID1 CustID = CustID1
In the following flat file lookup source, the keys are grouped, but not sorted. The Integration Service can cache the data, but performance may not be optimal.
OrderID
CustID
ItemNo.
ItemDesc
Comments
1001
CA502
F895S
Flashlight
Key data is grouped, but not sorted. CustID is out of order within OrderID.
1001
CA501
C530S
Compass
-
1001
CA501
T552T
Tent
-
1005
OK503
S104E
Safety Knife
Key data is grouped, but not sorted. OrderID is out of order.
1003
CA500
F304T
First Aid Kit
-
1003
TN601
R938M
Regulator System
-
The keys are not grouped in the following flat file lookup source. The Lookup transformation returns incorrect results.
OrderID
CustID
ItemNo.
ItemDesc
Comments
1001
CA501
T552T
Tent
-
1001
CA501
C530S
Compass
-
1005
OK503
S104E
Safety Knife
-
1003
TN601
R938M
Regulator System
-
1003
CA500
F304T
First Aid Kit
-
1001
CA502
F895S
Flashlight
Key data for CustID is not grouped.
If you choose sorted input for indirect files, the range of data must not overlap in the files.

0 COMMENTS

We’d like to hear from you!