![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I have a huge datawarehouse (atleast 300 million rows). I have seperate date and time dimensions(hour and minute attributes) to reduce dimension size. However most of our MDX queries are date range queries. The MDX this way gets a little complex. I have contemplated merging the date and time dimensions. Does anyone have any guidance on maximum dimension size(in term of number of rows)? |
#3
| |||
| |||
|
|
Hi, I have a huge datawarehouse (atleast 300 million rows). I have seperate date and time dimensions(hour and minute attributes) to reduce dimension size. However most of our MDX queries are date range queries. The MDX this way gets a little complex. I have contemplated merging the date and time dimensions. Does anyone have any guidance on maximum dimension size(in term of number of rows)? |
#4
| |||
| |||
|
|
the number of maximum members in AS2K is limited to 64K for each child members. I mean 1 member can have 64K children in AS2K, like 1 city can have 64K customers. if you have more then 64K members, you can add a level between the city and the customer level to split this 64K+ members into subsets of less then 64K members (like the first letter of the name of the customer) in AS2005 there is no issue like this. does your 300 millions of rows are for a dimension or for a fact table? if its a dimension, yes, its a big one... from a fact table point of view, its a good starting point, but not so big. from a date + time unique dimension, yes, its a good design. you just have to make sure that your aggregations and partitions are correctly setup to insure a good performance. "Mukesh Kumar" <MukeshKumar (AT) discussions (DOT) microsoft.com> wrote in message news:45CB411A-767D-489F-B9F7-D642E766E5EF (AT) microsoft (DOT) com... Hi, I have a huge datawarehouse (atleast 300 million rows). I have seperate date and time dimensions(hour and minute attributes) to reduce dimension size. However most of our MDX queries are date range queries. The MDX this way gets a little complex. I have contemplated merging the date and time dimensions. Does anyone have any guidance on maximum dimension size(in term of number of rows)? |
![]() |
| Thread Tools | |
| Display Modes | |
| |