performance between parent-child and regular

Which performance is batter between parent-child dimension and regular dimension in AS 2005?

thanks,In AS2005, as with AS2000, it's always better to use a regular dimension instead of a parent/child dimension if you can. In AS2000 using parent/child dimensions could have a significant impact on query performance, and while I haven't specifically tested whether this is still the case in AS2005 I've been told by one of the dev team that they will still perform relatively worse than regular dimensions.

Chris|||thank for your reply...

Performance between Hierarchy and Custom Member

Hi,

I have a simple dimension about product:

code, name, type
1111, coke, drink
1112, milk, drink
1113, coffee, drink
2111, cookieA, other
2112, cookieA, other

I can design a product dimension which has a hierarchy. Level 1 is type, and Level 2 is name. Then I can get total amount about drink and other. This design is the dimension which has a hierarchy.

However, I can design Custom Member to get total amount about drink and other:

code, name, CMColumn
1111, coke,
1112, milk,
1113, coffee,
2111, cookieA,
2112, cookieA,
9991, drink, ([Product].[1111]+[Product].[1112]+[Product].[1113])
9992, other, ([Product].[2111]+[Product].[2112])

Custom Member is designed instead of Hiearchy. The property "CustomRollupColumn" in dimension is set as CMColumn. So that I can get total amount about drink and other, too.

My question is which one's performance is better in the two designs?

thanks,

The first option has potentially better performance (if there are aggregations at the product type level), because queries for data at the type level could be directly answered from aggregations, rather than relying on rollups at runtime.|||

Deepak Puri wrote:

The first option has potentially better performance (if there are aggregations at the product type level), because queries for data at the type level could be directly answered from aggregations, rather than relying on rollups at runtime.

thanks.

I think the first option (using Hierarchy) costs more process time but less query response time.

The second option (using Custom Member) costs less process time but more query response time.

Is my opinion correct?

|||Probably correct - it depends on the dimension structure in the second option, and what aggregations are created for that structure...

Percentage measure

Hi,

easy question for advanced users:

I have a dimension called "Movement rate". The members are "1" to "6".
There is a measure called "No. of Products".

What i easily like to do is showing the percentages "No. of Product" for each "Movement rate" of the amount of "No. of Products" without using the frontend-tool.

Thx in advance for any help.

AndreasWhat is your table layout?|||Just for ur further explanation:

I like to get the following (red) result:

Movement rate No. of Products No. of Products in %
1 100 10
2 100 10
3 200 20
4 300 30
5 200 20
6 100 10
Amount: 1000 100

My table design is the following:

"Movement rate" int
"No of Products" int

I don't know for what reason u need this table design, cause what I need is the MDX - Query for my cube.

Thx.