Very Computer

Simon, if you are doing financial app, I recommend creating real dimension
members with Custom Rollup Formula instead of calculated members.
This way you can control ordering by carefully chosing member keys and
asking Analysis Services to sort dimension by key.

HTH,
Mosha.

--
==================================================
Mosha Pasumansky (moshap at microsoft dot com)
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Quote:> Crystal Analysis does allow users to add create calc members and
> change the order of dimension memebers but when user drills up or
> down, the ordering is lost and the default cube dimension order
> prevails. Can the cube be changed to overcome this problem?
> We have an issue with a dimension and calculated members that need to
> be ordered in a certain way: We have a finance cube and an object
> dimension and calculated
> members that needs to show in the following order:

> External Revenue
> Internal Revenue
> TOTAL REVENUE
> Expenditure
> TOTAL EXPENDITURE
> .
> .
> TOTAL PROFIT AND LOSS
> **Upper case show calculated members and rest are Object dimension
> members in the correct order.
> We have no issue sorting the object dimension members - we need to
> sort the calculated members with the object dimension members as above
> - any assistance appreciated.

Mosha,

I'm working with a financial application and calculated cells are doing
their job great. But I'm still not sure about performance. Which way of
calculating values (calculated cells, custom members, custom rollups or
calculated members) performs better?

Also is there any difference of setting the restrictions on the slice or on
the condition? (I think the slice performs better but this is just a
feeling. I'm asking this because the way we define slices is quite
restrictive).

Regards,

Paulo
"Mosha Pasumansky [MS]" <moshap at removethis microsoft dot com> wrote in

It is difficult to answer which of calculated cells, custom members, custom
rollups or calculated members performs better without knowing the exact
scenario. In general, calculated cells are the most generic and can do
anything that custom members, custom rollups, unary operators or calculated
members can do and then some more. Custom members are more convinient when
dimension is big, because the formulas are managed in the dimension table.
Calculated members have slightly different semantic then the rest, because
they never aggregate to parents.

For the second part - for performance reasons you need to avoid setting
formulas in the condition, and try to express your logic by using slice
only, even if it means creating several calculated cells with same
expression for different regions instead of one but with condition.

--
==================================================
Mosha Pasumansky (moshap at microsoft dot com)
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Quote:> Mosha,

> I'm working with a financial application and calculated cells are doing
> their job great. But I'm still not sure about performance. Which way of
> calculating values (calculated cells, custom members, custom rollups or
> calculated members) performs better?

> Also is there any difference of setting the restrictions on the slice or
on
> the condition? (I think the slice performs better but this is just a
> feeling. I'm asking this because the way we define slices is quite
> restrictive).

> Regards,

> Paulo