Sir, sorting condition was based on EMP ID , Distinct was also checked for same attribute , right ? so why Informatica is considering even First name Case sensitivity. It should simply look distinct emp_id ? or Distinct is applicable for every attributes ?
Yes I agree with @vishalchauhan9832 statement since we are sorting the data based on EMPID how come the case sensitive logic matters for EMPNAME..! @Goutham please explain..
![[UA] NAVI vs MOUZ | BO5 | IEM Rio 2024](http://i.ytimg.com/vi/CMBYk0cbGoA/mqdefault.jpg)
Sir Your voice is like Sachin Tendulkar 😂 but best INFORMATICA POWERCENTER Tutorial sir🎉❤
@@gouthams sir pls start IICS
Hii brother.....CASE SENSITIVE OPTION should always be in which condition....is it ON/OFF Condition....
Sir, sorting condition was based on EMP ID , Distinct was also checked for same attribute , right ? so why Informatica is considering even First name Case sensitivity. It should simply look distinct emp_id ? or Distinct is applicable for every attributes ?
Yes I agree with @vishalchauhan9832 statement since we are sorting the data based on EMPID how come the case sensitive logic matters for EMPNAME..! @Goutham please explain..
Sir I believe internally informatica is taking all the attributes for checking distinct records
@@sahilkhurana7923 acha 12 lpa pakka hai apka sir ji .
Can you please make video on unix/Linux in etl
(Why we use unix/Linux in etl testing and how to use unix/Linux in etl testing )