more than fact table and Hierarchy snowflake
2 posters
Page 1 of 1
more than fact table and Hierarchy snowflake
I am creating my new data warehouse for retail sales.
I have 2 fact tables “FastSFASales” and “FactTarget”
I have Item Hierarchy of product (Item / brand / family)
The FactSFASales are using Item as its granularity
Mean while FactTarget are using Brand as its granularity
So what I did is that I excluded the Brand and Family from DimItem to be on sperate DimFamily and DimBrand to server 2 facts tables.
Is there any other solution that will help me avoid the snowflake design?
Thanks,
i tried to put the link to my data warehouse sky drive but it is not allowed.
I have 2 fact tables “FastSFASales” and “FactTarget”
I have Item Hierarchy of product (Item / brand / family)
The FactSFASales are using Item as its granularity
Mean while FactTarget are using Brand as its granularity
So what I did is that I excluded the Brand and Family from DimItem to be on sperate DimFamily and DimBrand to server 2 facts tables.
Is there any other solution that will help me avoid the snowflake design?
Thanks,
i tried to put the link to my data warehouse sky drive but it is not allowed.
RamzyNashaat- Posts : 1
Join date : 2011-09-19
Re: more than fact table and Hierarchy snowflake
I introduced snowflaking in my DW to handle exactly this situation.
While it is possible (and perhaps even preferable) to model Brand as a mini-dimension related to Item only by conformed attributes, the BI tools that I've worked with (Microsoft SSAS and Business Objects) don't understand that relationship.
With snowflaked dimensions, the tools "undertand" that Item rolls up to Brand which rolls up to Family. The users can then drill across fact tables at different grains to compare actual sales to target.
There is a bit of a performance hit on queries, so I don't snowflake everything possible—only those dimension entities that are required (or are likely to be required in the near future) for facts at various grains.
While it is possible (and perhaps even preferable) to model Brand as a mini-dimension related to Item only by conformed attributes, the BI tools that I've worked with (Microsoft SSAS and Business Objects) don't understand that relationship.
With snowflaked dimensions, the tools "undertand" that Item rolls up to Brand which rolls up to Family. The users can then drill across fact tables at different grains to compare actual sales to target.
There is a bit of a performance hit on queries, so I don't snowflake everything possible—only those dimension entities that are required (or are likely to be required in the near future) for facts at various grains.
VHF- Posts : 236
Join date : 2009-04-28
Location : Wisconsin, US
Similar topics
» Why not snowflake if the aggregate dimension is needed for a different fact table?
» Combination of SCD2, partial snowflake, Effective and end dates in fact table
» Healthcare Hospital Stay fact table - transaction fact table - a row for In and a row for Out?
» 'Routing' the grain of the fact table to multpile members of multiple dimensions causes the fact table to 'explode'
» Integrating new fact table which has one to many relationship with the main fact table in existing star schema
» Combination of SCD2, partial snowflake, Effective and end dates in fact table
» Healthcare Hospital Stay fact table - transaction fact table - a row for In and a row for Out?
» 'Routing' the grain of the fact table to multpile members of multiple dimensions causes the fact table to 'explode'
» Integrating new fact table which has one to many relationship with the main fact table in existing star schema
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum