Major difference between SQL override and Lookup Sql override
- 1 Answers
- 2916 Views
- I also Faced
- E-Mail Answers
Answer Posted / ysindhureddy77@gmail.com
1. SQL Override is to limit the number of incoming rows entering the mapping pipeline
Lookup Override is to limit the number of lookup rows to avoid the whole table scan by saving the lookup time & cache it uses.
2. Lookup Override uses "Order By" clause by default
SQL Override doesn't uses it & should provide in our query if we require it.
3. SQL Override can provide any kind of join by writing the query
Lookup Override provides only Non-Equi joins
4. Lookup Override gives only one record even if it finds multiple records for a single condition
SQL Override doesn’t do that.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Differentiate between sessions and batches?
What is event and what are the tasks related to it?
How can you increase the performance in joiner transformation?
What are the components of Informatica? And what is the purpose of each?
How do you change a non-reusable transformation to reusable transformation?
TELL ME ONE COMPLEX MAPPING IN UR PROJECT? chandumba2005@gmai.com
where to store informatica rejected data?
What are pre and post-session shell commands?
Define update strategy?
Tell me any other tools for scheduling purpose other than workflow manager pmcmd?
How to elaborate tracing level?
What's the layout of parameter file (what does a parameter file contain?)?
can u give example for factless fact table
what is INFORMATICA TESTING process
Is stop and abort are same in informatica?
