sql server - SSAS 2012 - Dimension Modeling -


i working structure results lot of single attribute dimensions require no hierarchy. examples:

  • status(status name)
  • type(type name)

i following warning when compiling project:

"avoid having multiple dimensions containing single attribute. consider unifying them if possible."

a large number of single attribute dimensions workable our users, causes lot of clutter in excel pivot table. dimensions listed along single attribute redundant.

single attribute dimension

i unify them warning suggests have single dimension called 'attributes' contains status/type/etc, unsure best way so. doesn't make conceptual sense me parent/child dimension.

any suggestions?

i agree worthwhile change. construct view brings required attributes. available on fact/measure group table/view, can use same source object (in dsv) construct dimension.

the tricky part may dimension key. flexible key fact surrogate key eg unique value per fact row - in future can add other fact-based attributes without affecting key. not scale indefinitely - ok 1m rows @ least.

beyond scale, concatenate attributes form dimension key , deliver them new dimension table. in etl layer. identical concatenation logic must used both dimension , fact.


Comments

Popular posts from this blog

linux - Does gcc have any options to add version info in ELF binary file? -

android - send complex objects as post php java -

charts - What graph/dashboard product is facebook using in Dashboard: PUE & WUE -