 | |
Re: Why would NonEmptyCrossJoin fail on a virtual cube which joins
microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: Why would NonEmptyCrossJoin fail on a virtual cube which joins -
03-03-2005
, 04:04 PM
|
Is should be the dimension's default member. Does all MDX make it other way? Not that simple - default member is defined in the cube, but there is no cube here, because this dimension is outside of the cube. Default member could be a calculated member, which would obviously not work at all etc. When I said "consistent with the rest of MDX", I meant that normally MDX works with current coordinates, and there are rules about how to set it etc. Dimensions/levels not included in the cube are usually ignored, i.e. granularity is not set on them, except for the case when it is not possible not to set granularity - since there is no All level. I am not saying that I am 100% sure that there is no bug here, I am just saying, that unlike for you and for Chris - it is very non-obvious to me what the bug is and whether there is a bug. I still hope one of you can point me to the exact problem. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.