Interested to Buy Any Domain ? << Click Here >> for more details...
Major difference between SQL override and Lookup Sql override
- 1 Answers
- 4290 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
How to create a non-reusable instance of reusable transformations?
Enlist the tasks for which source qualifier transformation is used.
What is rank transform?
SOURCE DATA IS DISPLAY IN THIS FORMATE IN TARGET . WHAT BUSINESS LOGIC WE CAN APPLY. source table target table ------------ ------------ c1 c2 c3 c1 c2 c3 -- -- -- -- -- -- 1 A J 1 2 B K 2 A 3 C L 3 B J 4 D M 4 C K 5 E N 5 E L F M N
What is a connected transformation?
What is complex mapping?
How can you differentiate between powercenter and power map?
What is update strategy transform?
What is the maplet?
r u done any partitions in ur project?
can we override a native sql query within informatica? Where do we do it? How do we do it?
Implementation methodology
What are the designer tools for creating transformations?
What are the different components of powercenter?
What is rank transformation in informatica
