SQL Override and Lookup Override

If you write a SQL override in lookup transformation its a lookup override.

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....

Regards
Raj