We can configure a Lookup transformation to cache the lookup table. The Integration Service (IS) builds a cache in memory when it processes the first row of data in a cached Lookup transformation. The Integration Service also creates cache files by default in the $PMCacheDir. If the data does not fit in the memory cache, the IS stores the overflow values in the cache files. When session completes, IS releases cache memory and deletes the cache files.
Note:
- If we use a flat file lookup, the IS always caches the lookup source.
- We set the Cache type in Lookup Properties.
Lookup Cache Files:
- Lookup Index Cache: Stores data for the columns used in the lookup condition.
- Lookup Data Cache: For a connected Lookup transformation, stores data for the connected output ports, not including ports used in the lookup condition. For an unconnected Lookup transformation, stores data from the return port.
Types of Lookup Caches:
- Static Cache:
- Dynamic Cache:
- Persistent Cache:
- Recache from Source:
- Shared Cache:
- Unnamed cache: When Lookup transformations in a mapping have compatible caching structures, the IS shares the cache by default. You can only share static unnamed caches.
- Named cache: Use a persistent named cache when we want to share a cache file across mappings or share a dynamic and a static cache. The caching structures must match or be compatible with a named cache. You can share static and dynamic named caches.
By default, the IS creates a static cache. It caches the lookup file or table and looks up values in the cache for each row that comes into the transformation. The IS does not update the cache while it processes the Lookup transformation.
To cache a target table or flat file source and insert new rows or update existing rows in the cache, use a Lookup transformation with a dynamic cache. The IS dynamically inserts or updates data in the lookup cache and passes data to the target. Target table is also our lookup table. No good for performance if table is huge.
If the lookup table does not change between sessions, we can configure the Lookup transformation to use a persistent lookup cache. The IS saves and reuses cache files from session to session, eliminating the time required to read the lookup table.
If the persistent cache is not synchronized with the lookup table, we can configure the Lookup transformation to rebuild the lookup cache. If Lookup table has changed, we can use this to rebuild the lookup cache.
There are two types of Shared Cache. They are...
Great Article
ReplyDeleteArtificial Intelligence Projects
machine learning final year projects 2020
JavaScript Training in Chennai
JavaScript Training in Chennai Project Centers in Chennai
I have read your blog its very attractive and impressive. I like it your blog. Digital Marketing Company in Chennai
Lookup caches" are pivotal in data integration. They store previously retrieved data for quick retrieval, optimizing performance. The Silva Madden Whether in ETL processes or database queries, using lookup caches minimizes redundant lookups, enhancing efficiency.
ReplyDelete