![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |