Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...


What is the difference between warehouse key and surrogate key?



What is the difference between warehouse key and surrogate key?..

Answer / jaspreet banga

Surrogate key concept:- Surrogate keys are generated by
system and they identifies unique 'ENTITY'! yes its entity
and not record ,while primary key is used for finding
unique record.

Let me give you a simple classical example for surrogate
key:

On the 1st of January 2002 Employee 'E1' belongs to
Business Unit 'BU1' (that's what would be in your Employee
Dimension). This employee has a turnover allocated to him
on the Business Unit 'BU1' But on the 2nd of June the
Employee 'E1' is muted from Business Unit 'BU1' to Business
Unit 'BU2.' All the new turnover have to belong to the new
Business Unit 'BU2' but the old one should Belong to the
Business Unit 'BU1.'

If you used the natural business key 'E1' for your employee
within your datawarehouse everything would be allocated to
Business Unit 'BU2' even what actualy belongs to 'BU1.'

If you use surrogate keys you could create on the 2nd of
June a new record for the Employee 'E1' in your Employee
Dimension with a new surrogate key.

This way in your fact table you have your old data (before
2nd of June) with the SID of the Employee 'E1' 'BU1.' All
new data (after 2nd of June) would take the SID of the
employee 'E1' 'BU2.'

You could consider Slowly Changing Dimension as an
enlargement of your natural key: natural key of the
Employee was Employee Code 'E1' but for you it becomes
Employee Code Business Unit - 'E1' 'BU1' or 'E1' 'BU2.' But
the difference with the natural key enlargement process is
that you might not have all part of your new key within
your fact table so you might not be able to do the join on
the new enlarge key -> so you need another id.

Is This Answer Correct ?    3 Yes 1 No

Post New Answer

More Informatica Interview Questions

Can you use flat files in Mapplets.

0 Answers  


what are 3 tech challenges/ common issues you face?

0 Answers   TCS,


Hi Experts, Performance Wise Which transformation is better in LOOKUP AND JOINER TRansformations? Why? Can anybody please explain it ? Please help me out from this Question. Thanks In Advance.

2 Answers   CTS,


How to recover sessions in concurrent batches?

3 Answers  


why union transformation is active transformation?

6 Answers   IndiGo, TCS,


if the column name in sql override is diff from the column name in source qualifier,what is the impact?

5 Answers   TCS,


What is rank transform?

0 Answers  


How we can confirm all mappings in the repository simultaneously?

1 Answers  


update strategy transformation in informatica

0 Answers   Informatica,


Filter condition at workflow level & filter condition at mapping level . Which will get preference or which will work.

2 Answers  


can anyone suggest best free Talend data integration training online

0 Answers  


Why the workflow is failed after running two hours in informatica?

1 Answers   GE,


Categories