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

Guidelines for Sharing an Unnamed Lookup Cache

Guidelines for Sharing an Unnamed Lookup Cache

Use the following guidelines when you configure Lookup transformations to share an unnamed cache:
  • You can share static unnamed caches.
  • Shared transformations must use the same ports in the lookup condition. The conditions can use different operators, but the ports must be the same.
  • You must configure some of the transformation properties to enable unnamed cache sharing.
  • The structure of the cache for the shared transformations must be compatible.
    • If you use hash auto-keys partitioning, the lookup/output ports for each transformation must match.
    • If you do not use hash auto-keys partitioning, the lookup/output ports for the first shared transformation must match or be a superset of the lookup/output ports for subsequent transformations.
  • If the Lookup transformations with hash auto-keys partitioning are in different target load order groups, you must configure the same number of partitions for each group. If you do not use hash auto-keys partitioning, you can configure a different number of partitions for each target load order group.
The following table shows when you can share an unnamed static and dynamic cache:
Shared Cache
Location of Transformations
Static with Static
Anywhere in the mapping.
Dynamic with Dynamic
Cannot share.
Dynamic with Static
Cannot share.
The following table describes the guidelines to follow when you configure Lookup transformations to share an unnamed cache:
Properties
Configuration for Unnamed Shared Cache
Lookup SQL Override
If you use the Lookup SQL Override property, you must use the same override in all shared transformations.
Lookup Table Name
Must match.
Lookup Caching Enabled
Must be enabled.
Lookup Policy on Multiple Match
-
Lookup Condition
Shared transformations must use the same ports in the lookup condition. The conditions can use different operators, but the ports must be the same.
Connection Information
The connection must be the same. When you configure the sessions, the database connection must match.
Source Type
Must match.
Tracing Level
-
Lookup Cache Directory Name
Does not need to match.
Lookup Cache Persistent
Optional. You can share persistent and non-persistent.
Lookup Data Cache Size
Integration Service allocates memory for the first shared transformation in each pipeline stage. It does not allocate additional memory for subsequent shared transformations in the same pipeline stage.
Lookup Index Cache Size
Integration Service allocates memory for the first shared transformation in each pipeline stage. It does not allocate additional memory for subsequent shared transformations in the same pipeline stage.
Dynamic Lookup Cache
You cannot share an unnamed dynamic cache.
Output Old Value On Update
Does not need to match.
Cache File Name Prefix
Do not use. You cannot share a named cache with an unnamed cache.
Recache From Lookup Source
If you configure a Lookup transformation to recache from source, subsequent Lookup transformations in the target load order group can share the existing cache whether or not you configure them to recache from source. If you configure subsequent Lookup transformations to recache from source, the Integration Service shares the cache instead of rebuilding the cache when it processes the subsequent Lookup transformation.
If you do not configure the first Lookup transformation in a target load order group to recache from source, and you do configure the subsequent Lookup transformation to recache from source, the transformations cannot share the cache. The Integration Service builds the cache when it processes each Lookup transformation.
Lookup/Output Ports
The lookup/output ports for the second Lookup transformation must match or be a subset of the ports in the transformation that the Integration Service uses to build the cache. The order of the ports do not need to match.
Insert Else Update
-
Update Else Insert
-
Datetime Format
-
Thousand Separator
-
Decimal Separator
-
Case-Sensitive String Comparison
Must match.
Null Ordering
Must match.
Sorted Input
-

0 COMMENTS

We’d like to hear from you!