Composite Natural ID
3 posters
Page 1 of 1
Composite Natural ID
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
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
Re: Composite Natural ID
Separate. The basics of data modeling, storing one fact in one place, still hold true for dimensional models.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Re: Composite Natural ID
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.
Similar topics
» Composite Dimension Natural Keys - Attribute Used In Multiple Dimensions as well as Fact Tables
» Composite Keys - DIM
» Dimension Table with Composite Key
» when source contains surrogate key instead of natural key
» DW Key Vs Natural Key ?
» Composite Keys - DIM
» Dimension Table with Composite Key
» when source contains surrogate key instead of natural key
» DW Key Vs Natural Key ?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|