Interested to Buy Any Domain ? << Click Here >> for more details...
performance wise which one is better in joiner and lookup transformation?why?explain clearly?
- 4 Answers
- 21279 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 |
What are the different transaction levels available in transaction control transformation?
What are the different components of powercenter?
What are the basic requirements to join two sources in a source qualifier transformation using default join?
Hello...... How can i set my mapping as read-only? Please answer me. Advance thanks
What is power center repository?
What is Session and Batches?
what is unique constraint error ?
Why use the lookup transformation ?
write a query for how to eliminate the duplicate rows without using distinct?
Differences between version 7.x and 8.x.
0 Answers Accenture, Cognizant,
what is normalization? explain 1st NF, 2nd NF, 3rd NF
when we dont use aggregator in mapping ?
Teradata 
