dbTalk Databases Forums  

performance problem with writable cube

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


Discuss performance problem with writable cube in the microsoft.public.sqlserver.olap forum.



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

Default performance problem with writable cube - 03-14-2005 , 06:36 AM






hi all!

we are using a writable cube for budgeting purposes. the write table has
around 40.000 records now. when we open the cube after processing, it takes
around 5-10 mins to display the values. afterwards response time is ok, but
still not perfect. is there a way to optimize this without cleaning the
write table? could it help to change the fill-factor on the indexes msolap
automatically configures?

greetings
ref



Reply With Quote
  #2  
Old   
Ohjoo Kwon
 
Posts: n/a

Default Re: performance problem with writable cube - 03-14-2005 , 08:32 AM






I think it's best to convert writebacks to partition periodically.

Ohjoo Kwon


"ref" <re_f (AT) yahoo (DOT) com> wrote

Quote:
hi all!

we are using a writable cube for budgeting purposes. the write table has
around 40.000 records now. when we open the cube after processing, it
takes
around 5-10 mins to display the values. afterwards response time is ok,
but
still not perfect. is there a way to optimize this without cleaning the
write table? could it help to change the fill-factor on the indexes msolap
automatically configures?

greetings
ref





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

Default Re: performance problem with writable cube - 03-15-2005 , 04:05 AM



yes, thanks, this is what i did. after all its responding normally again.
crazy that msolap does not automaticaly include this data during cube
processing, but on runtime.

"Ohjoo Kwon" <ojkwon (AT) olap (DOT) co.kr> schrieb im Newsbeitrag
news:eY5R%23HKKFHA.2796 (AT) tk2msftngp13 (DOT) phx.gbl...
Quote:
I think it's best to convert writebacks to partition periodically.

Ohjoo Kwon


"ref" <re_f (AT) yahoo (DOT) com> wrote in message
news:%23ZbbAKJKFHA.3132 (AT) TK2MSFTNGP12 (DOT) phx.gbl...
hi all!

we are using a writable cube for budgeting purposes. the write table has
around 40.000 records now. when we open the cube after processing, it
takes
around 5-10 mins to display the values. afterwards response time is ok,
but
still not perfect. is there a way to optimize this without cleaning the
write table? could it help to change the fill-factor on the indexes
msolap
automatically configures?

greetings
ref







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.