Dear All,
Hope anyone can give me ideas on how to solve this problem.
I have a cube with some calculated measures. The application that access
this cube uses query-scope calculated member, for example to get the the
cancer incidence rate per 100,000 in 3 counties, the query would be:
WITH MEMBER [Geography].[AHierarchy].[NewCommunity] AS
SUM({[Geography].[AHierarchy].[COUNTY].&[Beaver],[Geography].[AHierarchy].[COUNTY].&[Allegheny],[Geography].[AHierarchy].[COUNTY].&[Washington]})
SELECT {[Geography].[AHierarchy].[NewCommunity]} ON COLUMNS ,
{[Year].[AHierarchy].[Year Id].&[2000]} ON ROWS
FROM [ExtendedDemo]
WHERE [Measures].[Cancer Incidence/100,000]
[Measures].[Cancer Incidence/100,000] is a calculated measure;
[Geography].[AHierarchy].[NewCommunity] is dynamic based on user selection.
Now the question is how to make calculation of member
[Geography].[AHierarchy].[NewCommunity] to be done before the calculation of
[Measures].[Cancer Incidence/100,000]. This query actually worked fine in
earlier beta version of SQL 2005 until we start using June CTP edition. I
tried to use the solve order attribute but it did not work.
Thanks a lot,
Wayan
Stan H - 17 Jan 2006 14:40 GMT
The November Release of AS2005 does NOT support intermingling of solve orders
of calculated members and/or calculated cells defined in the cube with those
defined in a query (or session). All calculations defined in the cube are
done before any that are defined in the query. (I believe session
calculations are done after cube and before query.)
We found this to be a major problem and have contacted MS for a fix. They
may be working on it. But it seemed a real surprise to them that someone
would really care about this feature. You may also note that the
documentation suggests that support for calculated cells is deprecated.
> Dear All,
>
[quoted text clipped - 20 lines]
>
> Wayan