MDX Guide for SQL Folks: Part II - Hierarchies and Functions

Question

MDX Guide for SQL Folks: Part II - Hierarchies and Functions

Frank A. Banin

SSCommitted

Points: 1727
More actions
December 18, 2012 at 12:01 am

#272201

Comments posted to this topic are about the item MDX Guide for SQL Folks: Part II - Hierarchies and Functions
Frank Banin
BI and Advanced Analytics Professional.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Ken SSCoach Points: 17191 More actions · Answer 1

Excellent article! The way you break down the MDX language is fantastic. These articles will definitely be book marked as training resources for our team.

Kevin Kunz-193240 Valued Member Points: 73 More actions · Answer 2

I remember back when I was first learning MDX I looked over so many books and sites that tried to teach MDX and none simplified it like this article, if only you had started this 2 years ago! Seriously well written!!

Cary Davis SSC Veteran Points: 245 More actions · Answer 3

Where was this article 2 years ago when I was beating my head against MDX? Probably the most helpful I've come across on the site. When I rated it I accidently fat fingered the rating and gave it 1 star! There's no way to go back and change it :blush:

robert.gerald.taylor SSChampion Points: 13133 More actions · Answer 4

Frank Banin (12/18/2012)
Comments posted to this topic are about the item <A HREF="/articles/MDX/91730/">MDX Guide for SQL Folks: Part II - Hierarchies and Functions </A>

Very good article.

There does seem to be a few typos in areas:

Missing &

SELECT

(

[Measures].[Internet Sales Amount]

,[Product].[Category].[Bikes]

,[Sales Territory].[Sales Territory Group].&[Europe]

,[Sales Territory].[Sales Territory Group].[North America]

,[Sales Territory].[Sales Territory Group]. [Pacific]

)

ON COLUMNS

FROM [Adventure Works];

should be:

SELECT

(

[Measures].[Internet Sales Amount]

,[Product].[Category].[Bikes]

,[Sales Territory].[Sales Territory Group].&[Europe]

,[Sales Territory].[Sales Territory Group].&[North America]

,[Sales Territory].[Sales Territory Group].&[Pacific]

)

ON COLUMNS

FROM [Adventure Works];

A missing comma after COLUMNS

SELECT

[Measures].[Internet Sales Amount] ON COLUMNS

{

[Sales Territory].[Sales Territory Group].&[Europe],

[Sales Territory].[Sales Territory Group].&[North America],

[Sales Territory].[Sales Territory Group].&[Pacific]

} ON ROWS

FROM [Adventure Works]

WHERE [Product].[Category].[Bikes];

None of these are big deals, but they will cause a person new to MDX some consternation.

Well done,

Rob

Frank A. Banin SSCommitted Points: 1727 More actions · Answer 5

KWymore and Kevin Kunz-193240, thanks for you comments coming from veterans like you. I guess after a while you get tired of some SSAS developers making MDX seem like rocket science. I consider myself a BI guy, but I spend a lot of time doing data integration using SSIS which normally constitute about 70% of most BI projects in my opnion. On a good BI project, a well designed cubes are normally just a reflection of a warehouse or Mart, there's nothing so special about it.

Frank Banin
BI and Advanced Analytics Professional.

Frank A. Banin SSCommitted Points: 1727 More actions · Answer 6

Cary Davis, No problem about the rating, it happens. I actually just added some skill set on my LinkedIn (http://www.linkedin.com/profile/view?id=11356645&trk=hb_tab_pro_top), an endorsement of MDX from any of you guys will be appreciated.

robert.gerald.taylor, thanks for catching those errors and the corrections.

Merry Christmas and a happy new year to you all.

Frank Banin
BI and Advanced Analytics Professional.