Major difference between SQL override and Lookup Sql override
- 1 Answers
- 3662 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
in reporting we add some new objects,how we get the count of the newly added objects to the report
What is difference between a gateway node and worker node?
Some flat files are there, out of these having some duplicate. How do you eliminate duplicate files while loading into targets?
What is sq transformation?
What are mapplets?
In informatica workflow manager, how many repositories can be created?
Can we create two repositories on same database instance in oracle?
What will be the approach?
What is event and what are the tasks related to it?
how to construct simple biogas digerter? please show me detail drawing and specification of simple biogas construction?
How does the aggregator transformation handle null values?
What are the limitations of joiner transformation?
What is the difference between SOURCE and TARGET BASED COMMITS? What are the deliverables?in your project?
how we can load rejected record's at run time?(not through bad files)
what is the -ve test case in your project.
