You can configure a Lookup transformation with a dynamic lookup cache to update the cache based on changes in the lookup source.
You might use a dynamic lookup cache for the following reasons:
Update a master customer table with new and updated customer information.
For example, you can use a Lookup transformation to perform a lookup on the customer table to determine if a customer exists in the target. The cache represents the customer table. The Lookup transformation inserts and update rows in the cache as it passes rows to the target.
Insert rows into a master customer table from multiple real-time sessions.
Use a Lookup transformation in each session to perform a lookup on the same customer table. Each Lookup transformation inserts rows into the customer table and it inserts them in the dynamic lookup cache. For more information about synchronizing dynamic cache between multiple sessions, see
GUID-8D12D72A-5FD1-4EF5-B9E8-81A8FEC5DEFA.
Load data into a slowly changing dimension table and a fact table.
Create two pipelines and configure a Lookup transformation that performs a lookup on the dimension table. Use a dynamic lookup cache to load data to the dimension table. Use a static lookup cache to load data to the fact table, and specify the name of the dynamic cache from the first pipeline.
Use an exported flat file as a lookup source instead of a relational table.
If the connection to the database is slow, you can export the relational table contents to a flat file and use the file as a lookup source. For example, you might need to use this method if an ODBC connection to a database is slow. You can configure the database table as a relational target in the mapping and pass the lookup cache changes back to the database table.