dbTalk Databases Forums  

Options for Working with Large Dimensions and dimension levels

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


Discuss Options for Working with Large Dimensions and dimension levels in the microsoft.public.sqlserver.olap forum.



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

Default Options for Working with Large Dimensions and dimension levels - 06-21-2006 , 10:10 PM






Any ideas on how to handle large levels?

I'm having performance issues when users try to add a dimension that has a
large level. I've already implemented grouping level but that does not help
with the performance when trying to access the data level.

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

Default Re: Options for Working with Large Dimensions and dimension levels - 06-22-2006 , 05:36 PM






which version of AS? (2000 or 2005)
how large is your dimension?
what do you mean by "data level"? do you talk about lowest level of the
cube?

optimize your aggregation design, partition your cube are the first steps to
do.

"SAM" <SAM (AT) discussions (DOT) microsoft.com> wrote

Quote:
Any ideas on how to handle large levels?

I'm having performance issues when users try to add a dimension that has a
large level. I've already implemented grouping level but that does not
help
with the performance when trying to access the data level.



Reply With Quote
  #3  
Old   
Wayne Snyder
 
Posts: n/a

Default Re: Options for Working with Large Dimensions and dimension levels - 06-23-2006 , 06:50 AM



SQL 2000 requires the entire dimension be loaded into memory when referenced,
which is often slow ( or even a stop if there is not enough memory.)

SQL 2005 does not require the complete load of the dimension, but large
dimension are still slow, especially in your case when there are many members
on the same level
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC

I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.


"Jeje" wrote:

Quote:
which version of AS? (2000 or 2005)
how large is your dimension?
what do you mean by "data level"? do you talk about lowest level of the
cube?

optimize your aggregation design, partition your cube are the first steps to
do.

"SAM" <SAM (AT) discussions (DOT) microsoft.com> wrote in message
news:E15FCF95-570B-4E99-807C-D6200F7F47DD (AT) microsoft (DOT) com...
Any ideas on how to handle large levels?

I'm having performance issues when users try to add a dimension that has a
large level. I've already implemented grouping level but that does not
help
with the performance when trying to access the data level.




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.