dbTalk Databases Forums  

Maximum Dimension Size

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Maximum Dimension Size in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mukesh Kumar
 
Posts: n/a

Default Maximum Dimension Size - 11-21-2006 , 04:02 PM






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)?



Reply With Quote
  #2  
Old   
Jesse O.
 
Posts: n/a

Default Re: Maximum Dimension Size - 11-21-2006 , 07:20 PM






It depends on which version of AS you are using.

AS2000 - 64k limit
SSAS2005 - no limit

"Mukesh Kumar" <MukeshKumar (AT) discussions (DOT) microsoft.com> wrote

Quote:
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)?





Reply With Quote
  #3  
Old   
Jeje
 
Posts: n/a

Default Re: Maximum Dimension Size - 11-21-2006 , 08:41 PM



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

Quote:
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)?



Reply With Quote
  #4  
Old   
Mukesh Kumar
 
Posts: n/a

Default Re: Maximum Dimension Size - 11-22-2006 , 11:31 AM



300 million rows are for the fact table.

I am using AS2005. With 2-3 years of detail date+time combined table will
have close to 2 million rows. Just wanted to make sure that it is not too big
for a dimension.

"Jeje" wrote:

Quote:
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)?



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.