Major difference between SQL override and Lookup Sql override
- 1 Answers
- 2954 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 the format of informatica objects in a repository?
In indirect file loading, suppose we have less no.of flat files then we can enter files names manually in list file creation. If millions of files are there, how can we enter the flat file names in list file?
Enlist few areas or real-time situations where informatica is required.
According to his methodology what all you need before you build a datawarehouse
write sql query following source table jan feb mar apr 100 200 300 400 500 600 700 800 900 100 200 300 i want the output format like month total jan 1500 feb 900 mar 1200 apr 1500
my source having 10 records but how can i load 20 records in target, i am not bother about duplicates?
In dimension and fact table? which one holds big data?
When you move from devel to prod how will you retain a variable
What is an incremental loading? in which situations we will use incremental loading
What is the session task and command task?
Label in Informatica. How to remove existing Label.
In informatica workflow manager, how many repositories can be created?
Teradata 
