Fact Measures at different grain levels


hi all,

need , suggestion in handling specific scenario.

i have fact table 1 shown below.  one order can have multiple  products related  quantity @ detail level shipontime ( value 1 or 0 )is @ order level.

created cube  qty  and shipontime as  measure sum aggregation type .

now if browse cube @ detail level works fine , qty and shipontime is coming out nice , if browse @ order level qty works fine shipontime create issues  it gives me sum of  detail level transaction.

is there way handle calculation or have design change cube ?

any appreciated.




adhikari707

you handle in several different ways, , choice depends on details of situation haven't heard yet. could, of course, move shipontime dedicated fact table or orders dimension table, , create either separate measure or calculation there. or change aggregation sum max, , handle need sum measure through mdx. or leave design , add necessary division mdx. or add physical measure aggregating count , calculation divide sum count.


SQL Server  >  SQL Server Analysis Services



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607