State the differences between sql override and lookup override?
Answer / Raju Sharma
SQL Override allows users to specify a custom query for the lookup instead of using the standard join operation. It is useful when dealing with complex data relationships or when the available join types do not meet your requirements. On the other hand, Lookup Override enables you to modify the behavior of the lookup transformation by specifying alternative settings such as changing the sort order, enabling or disabling caching, and controlling the handling of duplicate values.
| Is This Answer Correct ? | 0 Yes | 0 No |
1)can anyone explain how to use Normalizer transformation for the following scenario Source table | Target Table | Std_name ENG MAT ART | Subject Ramesh Himesh Mahesh Ramesh 68 82 78 | ENG 68 73 81 Himesh 73 87 89 | MAT 82 87 79 Mahesh 81 79 64 | ART 78 89 64 | please explain what should be the normalizer column(s) The GCID column 2)Also please explain the Ni-or-1 rule.
5 Answers FCS, IBM, Satyam, TCS,
i having mapping emp---> sq_emp--->target using this mapping i have to load dept table values into target... (condition assume there is no primary and foreign key relation between emp(table x) and dept (table Y))
What is limitations of truncate and load option
explain different levels in pushdown optimization with example?
In real time scenario where can we use mapping parameters and variables?
how can we perform incremental aggregation?explain with example?
can a port in expression transf be given the name DISTINCT
What is DR strategy for Informatica project?
How many input parameters can exist in an unconnected lookup?
Explain joiner transformation in informatica
I have a source as flat file and having data like ""TCS"MUMBAI" and i want output like TCS MUMBAI,the length of the data in the rows is variable.how can you fix it?
can anybody send me some real time screenshots of mapping in informatica powercenter. i will be vary thankful to him. my e-mail id :- prakashkumar.kumhar@gmail.com