Composite Natural ID

View previous topic View next topic Go down

Composite Natural ID

Post  tim_goodsell on Thu Dec 01, 2011 1:07 am

Hi

One of my dimensions has a composite natural id (Fund Code and Account Number), should I keep them separate in the dimension or concatenate them to form 1 natural id (e.g ."Fund Code-Account Number")

Regards

Tim


tim_goodsell

Posts : 49
Join date : 2010-09-21

View user profile

Back to top Go down

Re: Composite Natural ID

Post  BoxesAndLines on Thu Dec 01, 2011 10:37 am

Separate. The basics of data modeling, storing one fact in one place, still hold true for dimensional models.
avatar
BoxesAndLines

Posts : 1212
Join date : 2009-02-03
Location : USA

View user profile

Back to top Go down

Re: Composite Natural ID

Post  ngalemmo on Thu Dec 01, 2011 12:28 pm

I always do both, for exactly the same reasons B&L pointed out. A natural key column is a different column that serves a different purpose than the Fund Code and Account Number. The purpose of the dimensional attributes (Fund & Account) is to provide query attribute values in reports, the purpose of the natural key column is to identify a row for surrogate key assignment purposes. The two may be different, paticularly if the dimension needs to support multiple disparate data sources.
avatar
ngalemmo

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

View user profile http://aginity.com

Back to top Go down

Re: Composite Natural ID

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