Interested to Buy Any Domain ? << Click Here >> for more details...
Major difference between SQL override and Lookup Sql override
- 1 Answers
- 4382 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 |
How do you load more than 1 max sal in each department through informatica or write sql query in oracle?
What is hash partition?
what are the unix commands to start the wrk flow ?
What is the use of target designer?
Two workflows are running at same time first workflow is succeeded but second workflow is failed but there is no dependencies?
A mapping contains (1) Source Table S_Time ( Start_Year, End_Year ) (2) Target Table Tim_Dim ( Date, Day, Month, Year, Quarter )
I want to run a informatica worklow after complition of oracle procedure. That procedure is not running through informatica and can be run at any time in database. Informatica is in windows environment. Is it possible ? If yes please explain.
What is event and what are the tasks related to it?
What are the informatica performance improvement tips
How to load the data into target table, which not have Primary/Surrogate key (Duplicate records not acceptable)
What is Data Caches size?
Why touse stored procedure in ETL Application?
Teradata 
