You can configure the cache to permanently save the data. By default, the cache is created as non-persistent, that is, the cache will be deleted once the session run is complete. If the lookup table or file does not change across the session runs, you can use the existing persistent cache.
Suppose you have a process that is scheduled to run every day and you are using lookup transformation to look up on the reference table that which is not supposed to change for six months. When you use non-persistent cache every day, the same data will be stored in cache; this will waste time and space every day. If you select to create persistent cache, the integration service makes the cache permanent in the form of ...
