when source contains surrogate key instead of natural key

View previous topic View next topic Go down

when source contains surrogate key instead of natural key

Post  huny on Sun Mar 24, 2013 6:03 am

How to design dimension and facts when my source system table itself contains surrogate key (i mean auto generated id).......

for example:
EMP {
id PK
name
salary
designation
}

id is autogenerated sequence....... my dimension will contain this id as surrogate key but no natural key ...is it right?
if it is right then i cannot create key map table for my dimension

huny

Posts : 5
Join date : 2013-03-24

View user profile

Back to top Go down

Re: when source contains surrogate key instead of natural key

Post  ngalemmo on Sun Mar 24, 2013 6:10 am

A natural key is what the business uses to identify an entity. If the business is using this auto-generated number as the employee ID, then that is the natural key. It doesn't matter where the value comes from. Assign a surrogate key as you would with any natural key.
avatar
ngalemmo

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

View user profile http://aginity.com

Back to top Go down

Re: when source contains surrogate key instead of natural key

Post  huny on Sun Mar 24, 2013 6:16 am

ngalemmo wrote:A natural key is what the business uses to identify an entity. If the business is using this auto-generated number as the employee ID, then that is the natural key. It doesn't matter where the value comes from. Assign a surrogate key as you would with any natural key.

Thank You so much

huny

Posts : 5
Join date : 2013-03-24

View user profile

Back to top Go down

Re: when source contains surrogate key instead of natural key

Post  Sponsored content


Sponsored content


Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum