Professional Documents
Culture Documents
Performance Tuning in Informatica Using Peristent Cache
Performance Tuning in Informatica Using Peristent Cache
[Intended Audience: This paper expects the readers to have a fair knowledge of working with Informatica]
Table of contents
1
Content
Page No
1. Introduction...3 2. Looku transformation........3 3. !ethods to Im ro"e or tune Looku Transformation......# $. Use of ersistent cache in Looku ...% #. &'( )cenario * &ail+ load......, %. Conclusion......,. .ckno/ledgement10 1. 2eferences.10
2. Looku Transformation
Loo!up is a transformation to loo! up the values from a relational table*view or a flat file. The developer defines the loo!up match criteria. The categories of loo!up are connected + un,connected, static + dynamic. 'ifferent caches can also be used with loo!up li!e static, dynamic, persistent, and shared. Each of these has its own identification. Loo!up transformation is %assive and it can be both Connected and &nconnected as well. It is used to loo! up data in a relational table, view, or synonym. Loo!up definition can be imported either from source or from target tables. -or e"ample, if we want to retrieve all the sales of a product with an I' 1. and assume that the sales data resides in another table called /0ales/. (ere instead of using the sales table as one more source use Loo!up transformation to loo!up the data for the product, with I' 1. in sales table. In the Loo!up transformation, configure the following properties1
Looku condition3 3llows the Integration 0ervice to compare the input column containing codes with the loo!up table column. Looku )4L o"erride3 Ensures the Integration 0ervice e"tracts only loo!up table data that relates to input data. Looku cache3 3llows the Integration 0ervice to perform a loo!up 04L override. hen you configure a loo!up cache, you can configure the following cache settings1 5uilding caches1 5ou can configure the session to build caches se6uentially or concurrently. hen you build se6uential caches, the Integration 0ervice creates caches as the source rows enter the Loo!up transformation. hen you configure the session to build concurrent caches, the Integration 0ervice does not wait for the first row to enter the Loo!up transformation before it creates caches. Instead, it builds multiple caches concurrently. Persistent cache3 5ou can save the loo!up cache files and reuse them the ne"t time the Integration 0ervice processes a Loo!up transformation configured to use the cache. 2e cache from source3 If the persistent cache is not synchroni$ed with the loo!up table, you can configure the Loo!up transformation to rebuild the loo!up cache. )tatic cache3 5ou can configure a static, or read,only, cache for any loo!up source. 7y default, the Integration 0ervice creates a static cache. It caches the loo!up file or table and loo!s up values in the cache for each row that comes into the transformation. hen the loo!up condition is true, the Integration 0ervice returns a value from the loo!up cache. The Integration 0ervice does not update the cache while it processes the Loo!up transformation. &+namic cache3 To cache a table, flat file, or source definition and update the cache, configure a Loo!up transformation with dynamic cache. The Integration 0ervice dynamically inserts or updates data in the loo!up cache and passes the data to the target. The dynamic cache is synchroni$ed with the target. )hared cache3 5ou can share the loo!up cache between multiple transformations. 5ou can share an unnamed cache between transformations in the same mapping. 5ou can share a named cache between transformations in the same or different mappings.
Table Integration 0ervice (andling of %ersistent Caches Damed Cache Integration 0ervice cannot locate cache files. :ebuilds cache. Enable or disable the Enable (igh %recision option in session -ails properties. session. Edit the transformation in the Capping 'esigner, Capplet 'esigner, -ails or :eusable Transformation 'eveloper.E session. Edit the mapping ?e"cluding Loo!up transformation@. :euses cache. Change database connection or the file location used to access the -ails loo!up table. session. Change the Integration 0ervice data movement mode. -ails session. Change the sort order in &nicode mode. -ails session. Change the Integration 0ervice code page to a compatible code :euses page. cache. Change the Integration 0ervice code page to an incompatible code -ails page. session. Capping or 0ession Changes 7etween 0essions &nnamed Cache :ebuilds cache. :ebuilds cache. :ebuilds cache. :ebuilds cache. :ebuilds cache. :ebuilds cache. :ebuilds cache. :euses cache. :ebuilds cache.
EEditing properties such as transformation description or port description does not affect persistent cache handling.
In this mapping there is a dummy source and a dummy target. The flow is mainly used to create a loo!up cache.
The property Looku cache ersistent is enabled here, i.e. once the cache is built with the name ?l!pH'imH>rderH(eader@ specified in the property1 Cache 6ile Name Prefi78 it can be used across any other flow. 3lso here the property :e,cache from the loo!up source is enabled which means that every time the session runs, the cache will be re,built. The above cache can be used in another session as shown below.
3s the property Loo!up cache persistent is enabled, the cache with the name l!pH'imH>rderH(eader which is already built in the previous flow will be used.
%. Conclusion
&sing the performance tuning tips (igh performance capability of Informatica can be e"plored to meet the ever increasing user re6uirements and e"ploding data volumes.
,. .ckno/ledgement
3m than!ful to :ahul 'eshpande who has made some time from his busy schedule and helped me publishing the technical paper successfully.
1. 2eferences
1. Informatica wor! flow administration help manual. 2. Informatica portal.
1.