Modeling an attribute that belongs in more than one dimension
2 posters
Page 1 of 1
Modeling an attribute that belongs in more than one dimension
The fact table is transactions at a kiosk. The identification of the machine is qualified by the store where it is located. It is not identified uniquely without the store. The store is also part of the Location and owner dimensions.
What's the best way to model something like this?
Thanks in advance!
What's the best way to model something like this?
Thanks in advance!
Re: Modeling an attribute that belongs in more than one dimension
Include store as part of the natural key. You may also include store as an attribute of the dimension. The fact would carry store, kiosk, location & owner as dimensions.
Re: Modeling an attribute that belongs in more than one dimension
Thank you for the quick response!
There's an added complication, the device dimension is an SCD as the kiosk is configured to be different things and the configuration is relevant to the transaction. So, a natural key is, I guess, not applicable.
This is my first modeling project, so please forgive any unrefined assumptions and other stupidity. Add to that that "they" won't let me use actual scenarios and I'm forced to paint analogies while asking for help.
There's an added complication, the device dimension is an SCD as the kiosk is configured to be different things and the configuration is relevant to the transaction. So, a natural key is, I guess, not applicable.
This is my first modeling project, so please forgive any unrefined assumptions and other stupidity. Add to that that "they" won't let me use actual scenarios and I'm forced to paint analogies while asking for help.
Re: Modeling an attribute that belongs in more than one dimension
There is ALWAYS a natural key. Assuming the configuration is dynamic, you should implement a separate configuration dimension and use the kiosk dimension to identify the particular machine.
The configuration dimensions would be Type 1 and referenced from the fact identifying the configuration in place at the time of the transaction.
The configuration dimensions would be Type 1 and referenced from the fact identifying the configuration in place at the time of the transaction.
Re: Modeling an attribute that belongs in more than one dimension
I'm beginning to see the picture. Thank you!
Similar topics
» Customer Dimension Modeling - Level attribute
» Dimension Attribute or Fact Attribute
» DW Modeling - Should I use multiple value attribute with bridge?
» Modeling Descriptive Flex Fields (Attribute Columns) on an Order Line
» Separate dimension or dimension attribute
» Dimension Attribute or Fact Attribute
» DW Modeling - Should I use multiple value attribute with bridge?
» Modeling Descriptive Flex Fields (Attribute Columns) on an Order Line
» Separate dimension or dimension attribute
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum