![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Hi Chuck, You can refer to the MDX Solutions book (link below) for a deeper discussion of SOLVE_ORDER, but it typically needs to be tweaked when dealing with intersecting calculations along different dimensions. In your scenario, if you only need a calculated measure which averages the Quantity measure over time, SOLVE_ORDER shouldn't be a concern (assuming that summation over other dimensions is intrinsic to the Quantity measure). If you're using AS 2000, something like: Avg(Descendants([Time].CurrentMember, [Time].[Day]), [Measures].[Quantity) With AS 2005 Enterprise Edition, the Quantity measure could directly have "Average of Children" semi-additive behavior. MDX Solutions book link: http://www.wiley.com/WileyCDA/WileyT...471748080.html - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
#4
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |