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


Please Help Members By Posting Answers For Below Questions

I have three same source structure tables. But, I want to load into single target table. How do I do this? Explain in detail through mapping flow.

771


What is dimensional table? Explain the different dimensions.

655


How many ways a relational source definition can be updated and what are they?

577


What are the tuning techniques you applied during your last project

1561


if i hv 6 table as source table but can i make 12 as a dim table and 6 as fact table belongs to that src table.

1761






Explain the mapping variable usage example in informatica

631


What is confirmed fact in dataware housing?

5675


What is workflow? What are the components of workflow manager?

709


What are the advantages of using informatica as an etl tool over teradata?

565


Mention few advantages of router transformation over filter transformation.

633


Where are the source flat files kept before running the session?

624


How can we handle two sessions in informatica?

610


Differentiate between router and filter transformation?

613


Which transformation should we use to normalise the COBOL and relational sources?

740


What is meant by active and passive transformation?

584