![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Greetings All I have a question regarding how to show 2 dimensions on a cube that have different granularities in SQL 2k5AS Here is my setup Fact id snadi datetimeid CD DB Net Type 1 1 1 5 6 -1 A 2 2 1 55 66 -11 B etc. the granularity is as follows: the fact table will not have any duplicates based on type,snadi and datatimeid (in effect PK's) The measures are based on the type field, i.e. all the a in the above table make up one set of measures, all the b's and so on. Dimensions - DateTime links up on datatimeid and is a normal time dimension (taken from what Kimbal recommends). e.g. datetimeid year month, date............ 1 2000 1 2004 1/1/2005............ 2 2000 2 2004 3/1/2005............ The catch is that all A measures need to be aggregated in a year-quarter-month way and all B measures need to be aggregated using year-quarter-month-date way. Hence, 2 different granularities. I have gone thru the following paper http://blogs.msdn.com/bi_systems/articles/164185.aspx but still do not have a good and elegant solutions. Any suggestions would be appreciated. Regards PDI |
#3
| |||
| |||
|
|
AS 2005 supports the concept of mult-fact tables. You can see the case from Adventure Works sample under "C:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks Analysis Services Project\Enterprise" Go to the Dimension usage of cube designer and verify the setting of Date dimension of "Sales Target" measure group. Ohjoo Kwon "mma" <mma (AT) nospam (DOT) nospan> wrote in message news:4nbmn11f15e1auo96fbhf2uvck9g09uj6o (AT) 4ax (DOT) com... Greetings All I have a question regarding how to show 2 dimensions on a cube that have different granularities in SQL 2k5AS Here is my setup Fact id snadi datetimeid CD DB Net Type 1 1 1 5 6 -1 A 2 2 1 55 66 -11 B etc. the granularity is as follows: the fact table will not have any duplicates based on type,snadi and datatimeid (in effect PK's) The measures are based on the type field, i.e. all the a in the above table make up one set of measures, all the b's and so on. Dimensions - DateTime links up on datatimeid and is a normal time dimension (taken from what Kimbal recommends). e.g. datetimeid year month, date............ 1 2000 1 2004 1/1/2005............ 2 2000 2 2004 3/1/2005............ The catch is that all A measures need to be aggregated in a year-quarter-month way and all B measures need to be aggregated using year-quarter-month-date way. Hence, 2 different granularities. I have gone thru the following paper http://blogs.msdn.com/bi_systems/articles/164185.aspx but still do not have a good and elegant solutions. Any suggestions would be appreciated. |
#4
| |||
| |||
|
|
Just to expand a bit on the previous response. You would be better off splitting the A and B records into two separate tables. These would become to measure groups in an AS2k5 cube and you can link one to the date dimension based on month and the other based on days. HTH |
#5
| |||
| |||
|
|
Hi Thanks for the response. I thought of your suggestion. A question however, if you do that, how would you go about comparing A and B side by side in your cube? Basically, would there be any way of combining the 2 date dimensions into one so that you could drilldown all the way to the day level (I assume the dim that goes to the month level would not show)? pdi On Thu, 17 Nov 2005 16:57:40 +1100, Darren Gosbell jam (AT) newsgroups (DOT) nospam> wrote: Just to expand a bit on the previous response. You would be better off splitting the A and B records into two separate tables. These would become to measure groups in an AS2k5 cube and you can link one to the date dimension based on month and the other based on days. HTH |
![]() |
| Thread Tools | |
| Display Modes | |
| |