can you use flat file for lookup table?why?
Answers were Sorted based on User's Feedback
Answer / gyana
yes we can....we can definitly use the flat file as
lookup .....but we can not use the xml files as look
up...if u want to use then u have to change the xml file to
another database or flatfile..dn u can able to use
Is This Answer Correct ? | 8 Yes | 0 No |
Answer / gyana
yes we can....we can definitly use the flat file as
lookup .....but we can not use the xml files as look
up...if u want to use then u have to change the xml file to
another database or flatfile..dn u can able to use
Is This Answer Correct ? | 2 Yes | 0 No |
What is the filename which you need to configure in UNIX while installing infromatica?
rank() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid order by case when opt2.dm_market_flg in ('Y', 'U') then 1 else 2 end, lkp.contact_rank) as rank1, case opt2.contact_type when 'Buyer' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, ship_to_flg desc , last_order_dt desc) when 'Decision Maker' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc , last_quote_dt desc , mailability_score desc , source_ranking desc) when 'Influencer' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, mailability_score desc, source_ranking desc) when 'Payer' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, mailability_score desc, source_ranking desc) --elu 05/28/2013 else row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, mailability_score desc, source_ranking desc) end rank2 row_number() over (partition by opt3.dim_plat_site_id, opt3.dim_site_opt_sid order by rank1,rank2) as "rank", case when "rank"<= opt3.maximum_value then 'Y' else 'N' end as include_flg
what are the limitation of sorter transformation?
How the facts will be loaded? explain
what is constraint based loading
If i done any modifications for my table in back end does it reflect in informatca warehouse or maping desginer or source analyzer?
HOw can we load the normalised data ( Vertical data) to (Horizontal data)with out using decode in the expression transformation and the aggregator transformation. But, what exactly I want is .. If we have million of records,it is not possible using decode and search for that Particular Id to pivot into Horizontal data... Can any one of guys please help me in this regard.....
What is Story point Estimation ? Can any one give just an introduction about this ? Advance Thanks
Hi friends I want to know about what r the dimensions in the banking porjects and genarally how many tables r in project ?
Which transformation should we use to normalise the COBOL and relational sources?
for ex: in source 10 records are there with column sal. use a filter transformation condition as Sal=TRUE and connect to target. what will happen.
why we use stored procedure transformation?