![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have been fighting a battle to increase performance of a particular large dimension. I have reduced the dimension data members from over 200K to now 56K but I am still having performance issues when adding this dimension to the pivot. Is there a way to customize group levels? For instance, grouping by A-D, E-G, etc, that way if the user select a group from the drop down menu it will not take so long. Then possibly choosing what group to add to the pivot table to reduce the time it takes to query. I am running out of ideas to increase the performance of this particular dimension table. Any ideas? |
#3
| |||
| |||
|
|
the problem is related to the client application you display too many information. if you use an application which support a paging feature, you will be able to improve the display time. for example, try the cellsetgrid application and see the difference. another option is to not give access to this dimension, except through a drillthrough command,. or insure that you provide sheet (or analysis) allready setup with some filters and train the users to starts with other dimensions and use the biggest only as the latest dimension. Grouping A-D E.... etc is good too the user will drill down and display only a subset of members instead of the complete list. (as2000 provide an option to create this intermediate level for you automatically, or you can create it easely by using a an SQL statement like left(table.namecolumn, 1) ) good luck. "SAM" <SAM (AT) discussions (DOT) microsoft.com> wrote in message news:58E80E2D-89EC-4439-9FCD-70DB631B4105 (AT) microsoft (DOT) com... I have been fighting a battle to increase performance of a particular large dimension. I have reduced the dimension data members from over 200K to now 56K but I am still having performance issues when adding this dimension to the pivot. Is there a way to customize group levels? For instance, grouping by A-D, E-G, etc, that way if the user select a group from the drop down menu it will not take so long. Then possibly choosing what group to add to the pivot table to reduce the time it takes to query. I am running out of ideas to increase the performance of this particular dimension table. Any ideas? |
#4
| |||
| |||
|
|
The performance issue is present in the cube browser as well. Does that make a difference? In creating the groups, I created a automatic group in the dimension table but I did not see where you could customize the group to accomplish Grouping A-D, E...etc. I'll check again and test it. Thanks. I'll try the other suggestions as well. "Jeje" wrote: the problem is related to the client application you display too many information. if you use an application which support a paging feature, you will be able to improve the display time. for example, try the cellsetgrid application and see the difference. another option is to not give access to this dimension, except through a drillthrough command,. or insure that you provide sheet (or analysis) allready setup with some filters and train the users to starts with other dimensions and use the biggest only as the latest dimension. Grouping A-D E.... etc is good too the user will drill down and display only a subset of members instead of the complete list. (as2000 provide an option to create this intermediate level for you automatically, or you can create it easely by using a an SQL statement like left(table.namecolumn, 1) ) good luck. "SAM" <SAM (AT) discussions (DOT) microsoft.com> wrote in message news:58E80E2D-89EC-4439-9FCD-70DB631B4105 (AT) microsoft (DOT) com... I have been fighting a battle to increase performance of a particular large dimension. I have reduced the dimension data members from over 200K to now 56K but I am still having performance issues when adding this dimension to the pivot. Is there a way to customize group levels? For instance, grouping by A-D, E-G, etc, that way if the user select a group from the drop down menu it will not take so long. Then possibly choosing what group to add to the pivot table to reduce the time it takes to query. I am running out of ideas to increase the performance of this particular dimension table. Any ideas? |
![]() |
| Thread Tools | |
| Display Modes | |
| |