# Wednesday, September 21, 2005

I understand that its been quite sometime since last I posted to my blog. But rest assured for anyone still subscribing or reading my blog entries for good reason.

The last time I posted to this blog, I was slammed by fraud requests from “ebay” and “paypal,” and I also happened to graduate again from college with my bachelor’s degree in Software Engineering from Oregon Tech. Since then I’ve been engaged in another almost full time job brushing up on my skills with more reading and studying along with trying to land my first full-time programming job. So far things are looking very up, but as I was brushing up on my SQL skills, I happened across a rather convoluted data model.

If you have programmed with MDX other wise commonly known as Multidimensional Expressions query language, you probably then known what I’m taking about. The particular model uses Members, Tuples, and Sets to define a cubic style form of a data structure that from what I can gather, posses no form of relationships when compared to the Relational Data Model. I have to ask anyone reading this that if you have been able to glean one single ounce of useful amount of information using this Data Model SELECT statement construct:

   { [Measures].[Unit Sales], [Measures].[Store Sales] } ON AXIS(0),
   { [Time].[1997], [Time].[1998] } ON AXIS(1)
FROM Sales
WHERE ( [Store].[USA].[CA] )

I would very much like to hear your example, and how you were able to make it even REMOTELY useful?!?

Here is the core model for this rather convoluted data model:

Set Example:

Tuple Example:

Wednesday, September 21, 2005 10:08:01 PM UTC  #    Comments [0]Trackback
All comments require the approval of the site owner before being displayed.
Please login with either your OpenID above, or your details below.
(will show your gravatar icon)
Home page

Comment (HTML not allowed)  

Enter the code shown (prevents robots):

Live Comment Preview