which is better perfomancewise lookup or joiner and why?can anyone give example?
Answer Posted / pawan
R u looking for flat or database file?
Generally sorted joiner more effective on flat files than lookup, because sorted joiner uses merge join and cache less rows. Lookup caches always whole file. If the file is not sorted, it can be comparable. Lookups into DB table can be effective if the DB can return sorted data fast and the amount of data is small, because lookup can create whole cache in memory. If DB responses slowly or big amt of data r processed, lookup cache initialization can be really slow.
Then it can be better use sorted joiner, which throws data to output as reads them on input.
| Is This Answer Correct ? | 0 Yes | 2 No |
Post New Answer View All Answers
What is decode in static cache?
how can we find the bottle neck in SQL Query in SOURCE QUALIFIER, and how can we tune it..?
How do you remove duplicate records in informatica? And how many ways are there to do it?
Define joiner transformation?
What are the new features of informatica 9.x at the developer level?
How does a sorter cache works?
What are the advantages of using informatica as an etl tool over teradata?
define galaxy repository in informatica
How to create a non-reusable instance of reusable transformations?
What does refresh system mean, and what are its distinctive choice?
Explain what is informatica metadata and where is it stored?
What is option by which we can run all the sessions in a batch simultaneously?
What is a standalone command task?
Explain informatica architecture - version 8 / 9
What are active and passive transformations?