A couple of observations:
- If [Geography].[Region_Cd] and [Geography].[State_Cd] are attributes
which both appear in a user hierarchy like [Geography].[Region-State],
use this single heirarchy.
- Aggregating a calculated member may be problematic
An example of a user hierarchy in Adventure Works:
Member [Geography].[Country].[Country Set] as
Aggregate({[Geography].[State-Province].&[AL]&[US],
[Geography].[State-Province].&[AZ]&[US],
[Geography].[Country].&[Canada]})
select {[Measures].[Reseller Sales Amount]} on 0
from [Adventure Works]
where [Geography].[Country].[Country Set]
----------------------------------------------------
Members belong to different hierarchies in the function.
Member [Geography].[Country].[Country Set] as
Aggregate({[Geography].[Geography].[State-Province].&[AL]&[US],
[Geography].[Geography].[State-Province].&[AZ]&[US],
[Geography].[Geography].[Country].&[Canada]})
select {[Measures].[Reseller Sales Amount]} on 0
from [Adventure Works]
where [Geography].[Country].[Country Set]
----------------------------------------------------------
Reseller Sales Amount
$15,855,940.20
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.developersdex.com ***