SQL Override and Lookup Override

What is the difference between SQL Override and Lookup Override

Questions by purushotham.dwh

Showing Answers 1 - 4 of 4 Answers


  • Oct 13th, 2008

Obviously we have some differences between those 2 Overrides...

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 doen't do that...

Let me know if m wrong in any point....


  Was this answer useful?  Yes


  • Dec 20th, 2015

Can we have a different opinion on the 4th point?
"Lookup override gives only one record even though there..."
A lookup can return more than one record. We could handle this using the lookup property - "Lookup Policy on Multiple Match".

To handle all the rows that the lookup returns, we need to create the lookup transformation in the mapping using - "Return All values on Multiple Match" property enabled. Once you enable this property and create the transformation, the "Lookup Policy on Multiple Match" property will only have one option (selected by default) - "Use all Values".

  Was this answer useful?  Yes


  • Jan 2nd, 2016

You cannot use directly Union in Lookup Override. You can use in SQL Override. No join conditions in SQL Override. Join condition is compulsory in lookup.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions