Major difference between SQL override and Lookup Sql override
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 |
How Union Transformation is an Active Trans?
Can we write to_date(three arguments) ? Will it work ? Advance thanks
What are the mapping parameters and mapping variables?
Source (Flatfile) - Target (1-1 mapping). How to load first or last 20 record to target?
What are the features of complex mapping?
explain about lookup t/r?
Aggregator transformation is having fields say a,b,c,d,e group by is enabled on a,b,c with sorted input,How the aggregator transformation process the i/p data?or in which way i/p comes to agg transformation
where is the reject loader .
what is the logic will you implement to load data into a fact table from n dimension tables?
write a query following source region sales 1 1000 2 2000 i want the output ?please give solution 1 2 1000 2000
What do you mean incremental aggregation?
Which development components of informatica have the highest usage?