Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1


Ratings: (0)|Views: 145|Likes:
Published by MAHESH

More info:

Published by: MAHESH on Apr 04, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less





What are the differences between Connected and Unconnected Lookup?
Connected Lookup
Unconnected Lookup
 Connected lookup participates in dataflowand receives input directly from the pipelineUnconnected lookup receives input valuesfrom the result of a LKP: expression inanother transformationConnected lookup can use both dynamicand static cacheUnconnected Lookup cache can NOT bedynamicConnected lookup can return more than onecolumn value ( output port )Unconnected Lookup can return only onecolumn value i.e. output portConnected lookup caches all lookupcolumnsUnconnected lookup caches only the lookupoutput ports in the lookup conditions andthe return portSupports user-defined default values (i.e.value to return when lookup conditions arenot satisfied)Does not support user defined defaultvalues
What is the difference between Router and Filter?
 Router transformation divides the incomingrecords into multiple groups based on somecondition. Such groups can be mutuallyinclusive (Different groups may containsame record)Filter transformation restricts or blocks theincoming record set based on one givencondition.Router transformation itself does not block any record. If a certain record does notmatch any of the routing conditions, therecord is routed to default groupFilter transformation does not have a defaultgroup. If one record does not match filtercondition, the record is blockedRouter acts like CASE.. WHEN statementin SQL (Or Switch().. Case statement in C)Filter acts like WHERE condition is SQL.
What can we do to improve the performance of Informatica AggregatorTransformation?
Aggregator performance improves dramatically if records are sorted before passing to theaggregator and "sorted input" option under aggregator properties is checked. The record setshould be sorted on those columns that are used in Group By operation.It is often a good idea to sort the record set in database level(why?)e.g. inside a source qualifier transformation, unless there is a chance that already sorted records from source qualifier canagain become unsorted before reaching aggregator
What are the different lookup cache?
Lookups can be cached or uncached (No cache). Cached lookup can be either static or dynamic.A
static cache
is one which does not modify the cache once it is built and it remains same duringthe session run. On the other hand, A
dynamic cache
is refreshed during the session run byinserting or updating the records in cache based on the incoming source data.A lookup cache can also be divided as
based on whetherInformatica retains the cache even after session run is complete or not respectively
How can we update a record in target table without using Update strategy?
A target table can be updated without using 'Update Strategy'. For this, we need to define the keyin the target table in Informatica level and then we need to connect the key and the field we wantto update in the mapping Target. In the session level, we should set the target property as"Update as Update" and check the "Update" check-box.Let's assume we have a target table "Customer" with fields as "Customer ID", "Customer Name"and "Customer Address". Suppose we want to update "Customer Address" without an UpdateStrategy. Then we have to define "Customer ID" as primary key in Informatica level and we willhave to connect Customer ID and Customer Address fields in the mapping. If the sessionproperties are set correctly as described above, then the mapping will only update the customeraddress field for all matching customer IDs.
Deleting duplicate row using Informatica
Suppose we have
records in Source System and we want to load only the uniquerecords in the Target System eliminating the duplicate rows. What will be the approach?
 Let us assume that the source system is a
Relational Database
. The source table is havingduplicate rows. Now to eliminate duplicate records, we can check the
option of the
Source Qualifier
of the source table and load the target accordingly.
 Source Qualifier Transformation DISTINCT clause
Deleting duplicate row for FLAT FILE sources
Now suppose the source system is a
Flat File
. Here in the Source Qualifier you will not be ableto select the distinct clause as it is disabled due to flat file source table. Hence the next approachmay be we use a
Sorter Transformation
and check the
option. When we select thedistinct option all the columns will the selected as keys, in ascending order by default.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->