Interested to Buy Any Domain ? << Click Here >> for more details...
Major difference between SQL override and Lookup Sql override
- 1 Answers
- 4175 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
What are the types of schemas we have in data warehouse and what are the difference between them?
How do you load first and last records into target table? How many ways are there to do it? Explain through mapping flows.
What are mapplets? How is it different from a Reusable Transformation?
what is $$$$?
What is DR strategy for Informatica project?
How can we handle two sessions in informatica?
Hello, Can you please send the admin and advanced mapping design sample questions to ns_sharmin@yahoo.com?
How to update a particular record in target with out running whole workflow?
Define mapplet?
Explain where to store informatica rejected data? How to extract the informatica rejected data?
What is workflow? What are the components of the workflow manager?
What is substr in informatica?
Which means the first record should come as last record and last record should come as first record and load into the target file?
Explain lookup transformation source types in informatica
Make a note of the quantity vaults made in informatica?
