Interested to Buy Any Domain ? << Click Here >> for more details...
Major difference between SQL override and Lookup Sql override
- 1 Answers
- 4300 Views
- I also Faced
- E-Mail Answers
Answer / 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 |
What is workflow variable? When we use workflow variable? Can any one explain me with one example???
in performance wise union is past,union all is past
How to update a particular record in target with out running whole workflow?
What is informatica metadata and where is it stored?
What are the guidelines to be followed while using union transformation?
What is the grain level in DWH? If i have year to day. what is the grain level of DWH from year to day.
Performance tuning in UNIX for informatica mappings?
when will we go for unconnected lookup transformation in Informatica?
What is complex mapping?
In aggregator transformation, I sort the data before aggregator and select sorted port but still I’m getting an error. What is that error?
how we can load rejected record's at run time?(not through bad files)
how we do performence tuning in informatica
Teradata 
