What is the difference between SQL Override and Lookup Override?

Answer»

Lookup Override	SQL Override
By using Lookup Override, you can avoid scanning the WHOLE table by limiting the number of lookup rows, thus saving time and cache.	By using SQL Override, you can limit how many rows come into the mapping pipeline.
By default, it APPLIES the "ORDER By" clause.	When we need it, we need to manually add it to the query.
It only supports one kind of JOIN i.e., non-Equi join.	By writing the query, it can perform any kind of 'join'.
Despite finding multiple records for a single CONDITION, it only provides one.	This is not possible with SQL Override.

Discussion