More effective Set to Sum function?

I tested next two query and verified the same results.
The difference is different format_string is applied to CustTotal
automatically.

WITH
MEMBER Measures.CustTotal AS Sum({[Customer].[Customer
Geography].[Country].Members}*{[Measures].[Internet Sales Amount]})
SELECT
{CustTotal, [Internet Sales Amount]} ON 0,
{[Customer].[Country].Members} ON 1
FROM [Adventure Works];

WITH
MEMBER Measures.CustTotal AS Sum([Customer].[Customer
Geography].[Country].Members,[Measures].[Internet Sales Amount])
SELECT
{CustTotal, [Internet Sales Amount]} ON 0,
{[Customer].[Country].Members} ON 1
FROM [Adventure Works];

Here I'd like to know what is more effective and why it is.

Thanks in advance,

Ohjoo


.

Relevant Pages

  • Re: TOPCOUNT giving different results
    ... Against Adventure Works cube in Adventure Works DW SSAS database ... [Internet Sales Amount])) on 1 ... Query 1 Results: ... Internet Sales Amount ...
    (microsoft.public.sqlserver.olap)
  • TOPCOUNT giving different results
    ... Against Adventure Works cube in Adventure Works DW SSAS database ... [Internet Sales Amount])) on 1 ... Query 1 Results: ... Internet Sales Amount ...
    (microsoft.public.sqlserver.olap)
  • Re: More effective Set to Sum function?
    ... the SUM function is not required. ... MEMBER Measures.CustTotal AS Sum({.[Customer ... {CustTotal, [Internet Sales Amount]} ... FROM [Adventure Works]; ...
    (microsoft.public.sqlserver.olap)
  • Re: More effective Set to Sum function?
    ... Is there someone having difference opinion? ... MEMBER Measures.CustTotal AS Sum({.[Customer ... {CustTotal, [Internet Sales Amount]} ... FROM [Adventure Works]; ...
    (microsoft.public.sqlserver.olap)
  • RE: MDX Query Problem
    ... think you want to do in Adventure Works: ... MEMBER..TEST AS ... > Adventure Works - is trying to get a member in one dimension based on the key ... > EVERY step of the calculation. ...
    (microsoft.public.sqlserver.olap)