Cube Designing
2 posters
Page 1 of 1
Cube Designing
Hi,
While designing data source view in SSAS we are combing(Joining) fact and dimension table using T-sql and using it as a single fact.
Is it a correct design approach that we are joining FACT and Dimension using T-sql and using it as a Fact in the DSV of cube.
e.g,If I have Fact Internet sales and DimDate table then we are joining DimDate and Fact Internet sales using T-sql(for some reason) and using the result as a fact in Datasource view.
Please suggest.
While designing data source view in SSAS we are combing(Joining) fact and dimension table using T-sql and using it as a single fact.
Is it a correct design approach that we are joining FACT and Dimension using T-sql and using it as a Fact in the DSV of cube.
e.g,If I have Fact Internet sales and DimDate table then we are joining DimDate and Fact Internet sales using T-sql(for some reason) and using the result as a fact in Datasource view.
Please suggest.
Tridip- Posts : 1
Join date : 2012-05-02
Re: Cube Designing
Hello there.
Short answer, no it's not the correct design approach. Use the DimDate keys in facttable and reference it to the fact and let the cube do the joining and aggregations cause it will make it faster, smaller and easier to maintain.
Short answer, no it's not the correct design approach. Use the DimDate keys in facttable and reference it to the fact and let the cube do the joining and aggregations cause it will make it faster, smaller and easier to maintain.
Lindell- Posts : 6
Join date : 2011-08-02
Similar topics
» Newbie - designing data warehouse for cube
» SSAS Cube - zero downtime even during cube processing
» Designing for columnar database
» Designing a Fact for Sales DW
» star schema designing
» SSAS Cube - zero downtime even during cube processing
» Designing for columnar database
» Designing a Fact for Sales DW
» star schema designing
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum