| Author |
Slice Dimensions on Virtual Cubes
|
|
| Reuben 2005-09-26, 8:24 pm |
| I have a database that contains two virtual cubes. I am finding that when I
exectute MDX against one of the cubes (say cube A) I am getting dimensions
from the other cube (cube B) listed on the slice axis. Is this expected?
I am using Analysis services 2000 SP3 and the ODBO interface.
| |
|
| Hi Reuben,
Are these virtual cubes based on totally different actual cubes?
Ta
Paul
"Reuben" wrote:
> I have a database that contains two virtual cubes. I am finding that when I
> exectute MDX against one of the cubes (say cube A) I am getting dimensions
> from the other cube (cube B) listed on the slice axis. Is this expected?
>
> I am using Analysis services 2000 SP3 and the ODBO interface.
| |
| Reuben 2005-09-28, 8:24 pm |
| Hi Paul,
Turns out the problem is not quite as I stated it:
I have an ordinary cube. It has four dimensions. Two of which have the
visible property set to false. If I use the IDBSchemaRowset to get a list of
dimensions it (of course) only lists the visible ones.
However when I do an MDX query the MDAXISINFO lists the non-visible
dimensions on the slice axis.
Is this expected?
"Paul" wrote:
[color=darkred]
> Hi Reuben,
>
> Are these virtual cubes based on totally different actual cubes?
>
> Ta
> Paul
>
> "Reuben" wrote:
>
| |
| Darren Gosbell 2005-09-29, 3:24 am |
| This would be expected. If the dimensions physically exist, the values
would be stored in relation to them, the visibility property of the
dimension only hides them from client tools.
In order to resolve a value MDX needs to use a reference from every
dimension. The best way to think of it is like this - If you do not
specify a dimension in an MDX query you are actually implying that the
values should be sliced by the default member.
--
Regards
Darren Gosbell [MCSD]
< dgosbell_at_yahoo_do
t_com>
Blog: http://www.geekswithblogs.net/darrengosbell
In article <D951D50F-A4C3-4643-9757- CD4FB2CAA962@microso
ft.com>,
Reuben@discussions.microsoft.com says...
> Hi Paul,
>
> Turns out the problem is not quite as I stated it:
>
> I have an ordinary cube. It has four dimensions. Two of which have the
> visible property set to false. If I use the IDBSchemaRowset to get a list of
> dimensions it (of course) only lists the visible ones.
>
> However when I do an MDX query the MDAXISINFO lists the non-visible
> dimensions on the slice axis.
>
> Is this expected?
>
| |
| Reuben 2005-09-29, 8:24 pm |
| Hi Darren,
Thanks for your reply.
I can appreciate the conceptual point that the underlying cube still
contains these non-visible dimensions. However I have a problem with that
fact that one interface hides (correctly) these dimensions but another
doesn't. This means that a client application has to deal with the
incosicency between these two interfaces. Given that the clinet application
cannot discover these non-visible dimensions and therefore is not expected to
use them when creating queries etc. why does it get told about the
non-visible dimensions when the only thing it can possibly do with them is
ignore them?
"Darren Gosbell" wrote:
> This would be expected. If the dimensions physically exist, the values
> would be stored in relation to them, the visibility property of the
> dimension only hides them from client tools.
>
> In order to resolve a value MDX needs to use a reference from every
> dimension. The best way to think of it is like this - If you do not
> specify a dimension in an MDX query you are actually implying that the
> values should be sliced by the default member.
>
> --
> Regards
> Darren Gosbell [MCSD]
> < dgosbell_at_yahoo_do
t_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
>
> In article <D951D50F-A4C3-4643-9757- CD4FB2CAA962@microso
ft.com>,
> Reuben@discussions.microsoft.com says...
>
| |
| Darren Gosbell 2005-09-29, 8:24 pm |
| Not sure about that, your point makes sense to me. Maybe if someone from
MSFT is watching this thread they might chime in with an answer.
My only other thought is that if this is a single physical cube and you
don't want the users to see any reference to the dimensions in question,
why not just remove the dimensions from the cube?
I may be over simplifying things here, but removing dimensions from the
cube if they are not used will speed up the processing and query times.
--
Regards
Darren Gosbell [MCSD]
< dgosbell_at_yahoo_do
t_com>
Blog: http://www.geekswithblogs.net/darrengosbell
|
|
|
|