True, but recommended best practice is to run ProcessData followed by ProcessIndex rather than just running ProcessFull. The reasons for this are:

1. If, for example, the ProcessIndex fails, you can...

This is the same as doing a process full. Your optimal scenario depends on many things....

Assuming you have a hierarchy in your product dimension called Product then the following will give you the "All" member along with everything else:

[Product].[Product].Members

If you want to display just your...

If you are after what I think you are (the hierarchy outputted onto different columns for each level) then I don't think you can do that with MDX, it's not...

Firstly

http://weblogs.sqlteam.com/jeffs/archive/2008/05/13/question-needed-not-answer.aspx

😉

Secondly,

I think that you can achieve this with a combination of a For Each Loop Container and a variable for your file names. Or a script task if you're feeling...

Although 2005 doesn't have DMVs it is still compatible with the Analysis Services Stored Procedure library on codeplex: https://asstoredprocedures.codeplex.com/.

You'll find plenty of info in there in the CubeInfo class,...

Change the first part of your range in your calculation to Axis(1).Item(0)

So in AdventureWorks the example would be:

WITH

MEMBER Measures.toto AS

Aggregate({Axis(1).Item(0):[Date].[Date].currentmember},

[Measures].[Order Count])

SELECT

{[Measures].[Order Count], Measures.toto} ON 0,

NON EMPTY {[Date].[Date].&[20060301]:[Date].[Date].&[20060331]} ON 1

FROM

[Adventure...

Yes, Paul is indeed a great name 😀

Glad that it helped you out!

Hi Paul,

I think this may be a case for a little restructuring of your cube rather than more MDX trickery to be honest. Sorry to just give you another link,...

When you are browsing the cube I assume that you're doing so with some sort of measure? If so then by default (in the VS browser) then the non intersecting...

Glad to point you in the right direction.

Be careful of that LinkMember though :unsure:

From Chris Webb's blog (again): http://cwebbbi.wordpress.com/2011/05/24/replacing-linkmember-with-a-many-to-many-relationship/

vijay.singh 14112 (6/10/2014)

---

Hi John,

Please find the error message below.

Msg 3169, Level 16, State 1, Line 1

The database was backed up on a server running version 8.00.0760. That version is incompatible...

You'd most probably be better off putting your currency conversion logic within a SCOPE. Have a look at this article by Mosha Pasumansky on it: http://sqlblog.com/blogs/mosha/archive/2005/12/06/performance-of-multiplication-in-mdx.aspx

Or this one by Chriss...

Nearly there, just a small change:

STRTOMEMBER(

"[Date].[Date - CW].[Week].&["+CStr(year(Now()))+"]&["

CStr(year(Now()))+CStr(Datepart("ww", Now()))+"]"

)

You were missing a couple of elements 🙂

If you always want the current calendar week plus the two preceding it then you can construct the current week member by using a mixture of MDX and VBA. Then...