Misguided, probably. But an MDX Set does allow this sort of non-set like behavior. The following MDX, when run in Analysis Services, will produce 2 times the [unit sales] of [marital status].[m]:<br><br><br>with member [marital status].ASetIsNotASet as <br>
'Aggregate( {[Marital Status].[All Marital Status].[M], [Marital Status].[All Marital Status].[M] }, measures.[unit sales] )' <br>select {[marital status].ASetIsNotASet } on 0 from sales where measures.[unit sales]<br>
<br><div class="gmail_quote">On Jan 28, 2008 5:33 PM, John V. Sichi <<a href="mailto:jsichi@gmail.com">jsichi@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Ajit Vasudeo Joglekar wrote:<br>> 2) Aggregation of a normal (non distinct count) measure for select members<br>><br>> It is possible to get this working since it is very similar to case 1).<br>
> There is a issue here though. Lets say for whatever reason user wants to<br>> aggregate<br>><br>> Aggregate([Store].[All Stores].[USA].[CA], [Store].[All<br>> Stores].[USA].[CA], [Store].[All Stores].[USA].[OR]) over<br>
> [Measures].[Unit Sales]. The expected value here is (2 * CA + OR) for a<br>> non distinct count measure. The sql generated like above will not result<br>> in correct aggregation value<br><br></div>I don't see an issue here; the desire to "double-count" CA by including<br>
it in the set twice would be misguided, since a set is a set (no dups).<br><font color="#888888"><br>JVS<br></font><div><div></div><div class="Wj3C7c">_______________________________________________<br>Mondrian mailing list<br>
<a href="mailto:Mondrian@pentaho.org">Mondrian@pentaho.org</a><br><a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a><br></div></div></blockquote>
</div><br>