Should this be a degenerate dimension or a junk dimension?
2 posters
Page 1 of 1
Should this be a degenerate dimension or a junk dimension?
hi all -
we have a transaction table called disbursements and am creating a fact table off of this table. Most of the columns in this table are either keys to dimensions or measures which is good.
However, there are three columns that are texts:
- void indicator (Boolean)
- expense indicator (Boolean)
- Key off code (this is used to tie a disbursement with a purchase)
Should I put them in the fact table(degenerate dimension) or create a junk dimension(one for each indicator)? I am not sure how to deal with key off code.
Thanks in advance for helping out.
we have a transaction table called disbursements and am creating a fact table off of this table. Most of the columns in this table are either keys to dimensions or measures which is good.
However, there are three columns that are texts:
- void indicator (Boolean)
- expense indicator (Boolean)
- Key off code (this is used to tie a disbursement with a purchase)
Should I put them in the fact table(degenerate dimension) or create a junk dimension(one for each indicator)? I am not sure how to deal with key off code.
Thanks in advance for helping out.
SnowShine429- Posts : 36
Join date : 2013-02-16
Re: Should this be a degenerate dimension or a junk dimension?
Under no circumstances would I consider creating a junk dimension for each indicator. Replacing a simple boolean with an integer foreign key doesn't make sense.
You could create ONE junk dimension for all three attributes depending on what a 'key off code' is. Is this actually a reference to a specific transaction or is it a low cardinality classification code? If the latter, create one junk dimension with all three attributes. If it is a transaction reference store it as a degenerate dimension. At which point, since you have only two boolean's left over, keep those as degenerate dimensions as well.
You could create ONE junk dimension for all three attributes depending on what a 'key off code' is. Is this actually a reference to a specific transaction or is it a low cardinality classification code? If the latter, create one junk dimension with all three attributes. If it is a transaction reference store it as a degenerate dimension. At which point, since you have only two boolean's left over, keep those as degenerate dimensions as well.
Similar topics
» Should I use a degenerate dimension or create a junk dimension?
» bridge table and junk dimension on customer dimension (bank/credit union)
» modelling Product dimension for Pizza outlet
» Question on breaking out Degenerate Dimension to separate dimension
» "Junk" dimension looking more like a "Header" dimension
» bridge table and junk dimension on customer dimension (bank/credit union)
» modelling Product dimension for Pizza outlet
» Question on breaking out Degenerate Dimension to separate dimension
» "Junk" dimension looking more like a "Header" dimension
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum