performance wise which one is better in joiner and lookup transformation?why?explain clearly?
- 4 Answers
- 19755 Views
- IBM, I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
How to do unit testing in informatica?
what is the -ve test case in your project.
what is diff b/t sorter t/r and agg have the option sorter property...
how lookup transformation is made active in new versions... When to use connected and when to use unconnected lookup and why? which is good for session performance. How to make lookup persistent and how to remove stale data from that lookup. how commit works - when we stop or abort data. Explain in both cases. What is factless fact table and have you ever used it in real time scenarios.
wf dont have integration severances how you can run?
How many transformations can be used in mapplets.
What is an Integration service in Informatica?
Briefly define a session task?
Describe an informatica powercenter?
I have 100 records in source table, but I want to load 1, 5,10,15,20…..100 into target table. How can I do this? Explain in detailed mapping flow.
Is stop and abort are same in informatica?
How you can differentiate between connected lookup and unconnected lookup?
Can we override a native sql query within informatica?
How to handle decimal places while importing a flatfile into informatica?
How can informatica be used for an organization?
