Multi-Level Dimension
3 posters
Page 1 of 1
Multi-Level Dimension
Hello
I am constructing an Working Status Dimension that will contain the following
Working Status Group Working Status
EMPLOYED FULLTIME
CASUAL
PARTTIME
UNEMPLOYED CEASED
RETIRED
OTHER
Is it best to have a parent key in the dimension record so that the record representing the status (e.g "Employed - Full Time" will have a parent key pointing to the parent record "Employed" or keep everthing in one record (see below)
Key Description Group
1 Unknown Unknown
2 Employed - Full Time Employed
3 Employed - Casual Employed
4 Employed - Part Time Employed
5 Unemployed - Ceased Unemployed
6 Unemployed - Retired Unemployed
7 Unemployed - Other Unemployed
Regards
Tim
I am constructing an Working Status Dimension that will contain the following
Working Status Group Working Status
EMPLOYED FULLTIME
CASUAL
PARTTIME
UNEMPLOYED CEASED
RETIRED
OTHER
Is it best to have a parent key in the dimension record so that the record representing the status (e.g "Employed - Full Time" will have a parent key pointing to the parent record "Employed" or keep everthing in one record (see below)
Key Description Group
1 Unknown Unknown
2 Employed - Full Time Employed
3 Employed - Casual Employed
4 Employed - Part Time Employed
5 Unemployed - Ceased Unemployed
6 Unemployed - Retired Unemployed
7 Unemployed - Other Unemployed
Regards
Tim
tim_goodsell- Posts : 49
Join date : 2010-09-21
Re: Multi-Level Dimension
Keep it all in one record (row). I think you're asking whether snowflaking is a good idea and the answer to that is no.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Recursion
Thanks for that, I was thinking more of recursion, a key in the table pointing to the primary key of the same dimension rather than having a separate dimension for the group attributes
tim_goodsell- Posts : 49
Join date : 2010-09-21
Re: Multi-Level Dimension
I don't follow why you would want a recursion here. The situation is far too simple for that.
You basically have a handful of statuses. There is no hierarchy. The fact that some represent employed or not employed is usually represented as attributes of the status.
You basically have a handful of statuses. There is no hierarchy. The fact that some represent employed or not employed is usually represented as attributes of the status.
Similar topics
» Transaction with Multi level Hierarchy
» Multi level grainulity in Fact table
» Replacing Aggregate dimension with Conformed base dimension at lowest level.
» Problem with multi-valued Dimension
» Multi enterprise Calendar Dimension
» Multi level grainulity in Fact table
» Replacing Aggregate dimension with Conformed base dimension at lowest level.
» Problem with multi-valued Dimension
» Multi enterprise Calendar Dimension
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum