performance wise which one is better in joiner and lookup transformation?why?explain clearly?
- 4 Answers
- 19703 Views
- IBM, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / krishna
joiner is best because we will make less number of records or dublicate records as master. integration servic create cahce for master table. becaue of that cahce size is small and secarching oricess become easy. in case of lookup its should scane om botom to end it will take more time.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / basha
based on the situation if we need to cache concept we will
use lkp tr ,we doesnot need to caches we use joiner tr
performence wise joiner is better
| Is This Answer Correct ? | 1 Yes | 5 No |
Answer / rampriya
Joiner is faster than lookup. Joiner will fetch the data
only once form the database, but the lookup will fetch the
data for each record from the database. So performance wise
joiner is better than lookup.
| Is This Answer Correct ? | 4 Yes | 13 No |
How is union transformation utilized?
What is intricate mapping?
Can we write to_date(three arguments) ? Will it work ? Advance thanks
difference between source based commit? and target based commit? which is better with respect to performance?
What are the types of maping in Getting Started Wizard?
What is the advantage of informatica?
what is data driven?
Suppose on 1st Nov 2010 you had created a mapping which includes huge aggregator calculations and it is under process for next two days. You will notice that even on 3rd day also its still calculating. So without changing a logic or changing a mapping How will you troubleshot or to run that mapping? Explain the steps
design of staging area?
what is the difference between onsite & client site?
What is a grid in Informatica?
Explain about perform recovery?
Teradata 
