Y/N fields in dimension or as measure with 0 and 1 (or both)?
3 posters
Page 1 of 1
Y/N fields in dimension or as measure with 0 and 1 (or both)?
I've a couple of Y/N fields and i've translated them into 0 and 1 for summarizing the results. Now my customers are telling me they can't select on measures (in Excel/cube). I'm thinking to build a Factdimension (in SSAS) with these Y/N fields.
I'm thinking about building them both..
Is this correct?
Hennie
I'm thinking about building them both..
Is this correct?
Hennie
hennie7863- Posts : 31
Join date : 2009-10-19
Re: Y/N fields in dimension or as measure with 0 and 1 (or both)?
First of all, these flags are dimensions with very low cardinality. So combining them into a junk dimension makes perfect sense.
If you want to derive some measures out of the junk dimension for the cube, you could always do that in a fact view so you still have the junk dimension key for each record in the view.
If you want to derive some measures out of the junk dimension for the cube, you could always do that in a fact view so you still have the junk dimension key for each record in the view.
hang- Posts : 528
Join date : 2010-05-07
Location : Brisbane, Australia
Re: Y/N fields in dimension or as measure with 0 and 1 (or both)?
There are a dimension, not a measure. Whether you include them in a junk dimension or not, they should be renamed to something descriptive e.g. for an attribute of ManagedFund the values should be not be Y/N but rather Managed Fund, Unmanaged Fund.
Similar topics
» Popluate two measure fields in fact table from same SCD2 dimenion attribute
» Dimension fields depend on other fields
» Volume and Weight in Same Fact Table
» Always link date fields to Date Dimension?
» employee dimension - adding extra fields
» Dimension fields depend on other fields
» Volume and Weight in Same Fact Table
» Always link date fields to Date Dimension?
» employee dimension - adding extra fields
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum