![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Hi Clint, Could you provide more specifics about the MDX you're using, the structure of the time hierarchy, and the nature of errors or incorrect results that you get? - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
#4
| |||
| |||
|
#5
| |||
| |||
|
#6
| |||
| |||
|
| With Member [Measures].[RunningSales] as |
#7
| |||
| |||
|
#8
| |||
| |||
|
| With Member [Measures].[Cumulative Sales Amount] as |
#9
| |||
| |||
|
|
Clint, After experimenting with AS 2005 Adventure Works, there seems to be a quirk in PeriodsToDate() behavior (versus AS 2000) which I can't quite explain: if only a [Date].[Calendar] level is specified, but no member, it returns members from the [Date].[Fiscal] hierarchy instead. So, explicitly specify [Date].[Calendar].CurrentMember, like: With Member [Measures].[Cumulative Sales Amount] as Sum(PERIODSTODATE([Date].[Calendar].[(All)], [Date].[Calendar].CurrentMember), [Measures].[Reseller Sales Amount]) Select {[Measures].[Reseller Sales Amount], [Measures].[Cumulative Sales Amount]} on 0, [Date].[Calendar].[Month].Members on 1 from [Adventure Works] - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
![]() |
| Thread Tools | |
| Display Modes | |
| |