Shrunken Dimension: Model and loading
3 posters
Page 1 of 1
Shrunken Dimension: Model and loading
Hello:
We have the following model:
Fact_Order->Dim_Item
Dim_Item contains the attributes Item,Subcategory and Category
Now we have to load two new facts:
Fact_Budget: Category level
Fact_Invoice: SubCategory Level
What we have to do? Create two new dimensions Dim_Category and Dim_Subcategory from Dim_Item? We have to repeat the values of category on Dim_Subcategory for example?
Thanks
We have the following model:
Fact_Order->Dim_Item
Dim_Item contains the attributes Item,Subcategory and Category
Now we have to load two new facts:
Fact_Budget: Category level
Fact_Invoice: SubCategory Level
What we have to do? Create two new dimensions Dim_Category and Dim_Subcategory from Dim_Item? We have to repeat the values of category on Dim_Subcategory for example?
Thanks
jldosil- Posts : 3
Join date : 2011-09-19
Re: Shrunken Dimension: Model and loading
Invoicing is typically at the line level, which is usually item. If you are aggregating the source at the sub category level, I would suggest you don't.
But if that is what you have, then yes, you would create category and sub category dimensions. I would populate category info in the sub category dimension.
But if that is what you have, then yes, you would create category and sub category dimensions. I would populate category info in the sub category dimension.
Re: Shrunken Dimension: Model and loading
Thank you ngalemmo.
Our invoicing System donīt record transactions at Item level. We always load the maximum grain available (thank you "The Data Warehouse Toolkit")
Another question, our BI tool recommends (God knows why) a snowflake schema (in fact modeling a star schema is more complicated in the tool).
Have any sense to you, loading the dimensions in snowfalke style, (i mean, Dim_Item only contains Item and surrogate key to Dim_Subcategory that contais only Subcategory info and surrogate key to Dim_Category...), and then create materialized views for resolving the "star dimensions". I mean, the joins with the fact always be through the materialized views (only a join) due to query rewriting.
Is that still a Star Schema? Its just an idea, i donīt know if it make sense.
Thanks again.
Our invoicing System donīt record transactions at Item level. We always load the maximum grain available (thank you "The Data Warehouse Toolkit")
Another question, our BI tool recommends (God knows why) a snowflake schema (in fact modeling a star schema is more complicated in the tool).
Have any sense to you, loading the dimensions in snowfalke style, (i mean, Dim_Item only contains Item and surrogate key to Dim_Subcategory that contais only Subcategory info and surrogate key to Dim_Category...), and then create materialized views for resolving the "star dimensions". I mean, the joins with the fact always be through the materialized views (only a join) due to query rewriting.
Is that still a Star Schema? Its just an idea, i donīt know if it make sense.
Thanks again.
Last edited by jldosil on Fri Aug 07, 2015 11:44 am; edited 1 time in total
jldosil- Posts : 3
Join date : 2011-09-19
Re: Shrunken Dimension: Model and loading
if you go with create two Dimensions from the d_item.. than your d_item will be role playing . I think you create a view for category and subcategory and use that in your respective fact tables.
and that would be still start schema.
and that would be still start schema.
sharvan.kumar.83@gmail.co- Posts : 10
Join date : 2014-11-17
Similar topics
» Shrunken Dimension for Drilling across Fact Tables
» Dimension loading sources
» Loading fact table and dimension indexing.
» Loading dimension when source already has effective to and from dates
» How to model IP Dimension
» Dimension loading sources
» Loading fact table and dimension indexing.
» Loading dimension when source already has effective to and from dates
» How to model IP Dimension
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|