Rules and Guidelines for Dynamic Caches

The Lookup transformation must be a connected transformation.

· You can use a persistent or a non-persistent cache.
· If the dynamic cache is not persistent, the Informatica Server always rebuilds the cache from the database, even if you do not enable Recache from Database.

· You cannot share the cache between a dynamic Lookup transformation and static Lookup transformation in the same target load order group.

· You can only create an equality lookup condition. You cannot look up a range of data.

· Associate each lookup port (that is not in the lookup condition) with an input port or a sequence ID.

· Only connect lookup/output ports to the target table instead of input/output ports. When you do this, the Informatica Server writes the same values to the lookup cache and the target table, keeping them synchronized.

· When you use a lookup SQL override, make sure you map the correct columns to the appropriate targets for lookup.

· When you add a WHERE clause to the lookup SQL override, use a Filter transformation before the Lookup transformation. This ensures the Informatica Server only inserts rows in the dynamic cache and target table that match the WHERE clause. For details, see Using the WHERE Clause with a Dynamic Cache.

· When you configure a reusable Lookup transformation to use a dynamic cache, you cannot edit the condition or disable the Dynamic Lookup Cache property in a mapping.

· Use Update Strategy transformations after the Lookup transformation to flag the rows for insert or update for the target.

· Use an Update Strategy transformation before the Lookup transformation to define some or all rows as update if you want to use the Update Else Insert property in the Lookup transformation.

· Set the row type to Data Driven in the session properties.
·

Select Insert and Update as Update for the target table options in the session properties.