I know this is not a supported scenario in Analysis Services 2005 but i just
wanted to know if anyone had same requirements and have a solution for it.
Thanks.

Can you be a bit clearer about what you want to do? If you're talking about
regular dimensions then if you have members which you think should exist
together, then perhaps you should think about combining the dimensions.
However, I can think of other scenarios (eg with many-to-many dimensions)
where you would like members from different dimensions to autoexist.

Anyway, the fact remains that you can't do autoexist across dimensions. You
now have two different options in MDX though to test whether combinations of
members exist together in the fact table though. You can either crossjoin two
sets together and get rid of the empty members, for example:

SELECT [Measures].[Internet Sales Amount] ON 0,
NON EMPTY
[Customer].[Customer].[Customer]
*
[Date].[Calendar].[Date].&[915]
ON 1
FROM
[Adventure Works]

Or you can use the new EXISTS() function, which does something slightly
different - it will return all the combinations that exist in the fact table
even if all the measure values for that combination are null (see
http://sqljunkies.com/WebLog/mosha/a.../02/13315.aspx for more
details), for example:

SELECT [Measures].[Internet Sales Amount] ON 0,
EXISTS(
[Customer].[Customer].[Customer]
,
[Date].[Calendar].[Date].&[915]
, "Internet Sales")
ON 1
FROM
[Adventure Works]

hth,

Chris

--
Blog at:
http://spaces.msn.com/members/cwebbbi/


"Resho" wrote: