Hi,

Is it correct to assume that MDX queries that were developed to work against
AS2000 will work the same against Analysis Services Yukon?

Thanks.

Sort of - note the fact that while AS2k has a dimensional model, AS2k5
(Yukon) has an attribute/hierarchy model. If you did a straight up
migration of the OLAP cube from AS2k to AS2k5, you are probably okay but you
will still need to insure that nothing wierd happened during the migration
since you are going from one model to another. The main thing you have to
worry about is that you may need refer to your dimensions what was
originally in AS2k [Dimension].children to [Dimension].[Hierarchy].children
in AS2k5. Saying this, if you are doing a straight up migration, then you
most likely do not need to worry about this because there will only be one
hierarchy for the dimension.

--
HTH!
Denny Lee
<dennyglee_at_hotmail_dot_com>

Blog at:: http://spaces.msn.com/members/denster/



"Jimmy" <NoSpam> wrote

Thanks for your reply, Denny.

How is that different from AS2000? Dimensions in 2K are made up of
hierarchies as well. Unless I'm mistaken, [Dimension].Children can be used
in 2K only if the dimension has a single hierarchy, both in 2K and 2K5.

My question pertains mainly to the development of a client application
against 2K5 in comparison to the same development against 2K. Is there any
difference in terms of:

*) Browsing/Displaying the dimensional tree.
*) MDX logic.
*) The way results are returned.

Many thanks!

"Denny Lee" <dennyglee (AT) hotmail (DOT) com> wrote

From a UI perspective, there are only a few differences and it really has to
do with the fact that you have to indicate the hierarchies. When Excel 2003
(using the Yukon driver) accesses an AS2k5 cube, it will have access to both
the hierarchies (similar to AS2k) and the attributes. Accessing the
attributes provides you with a much larger list within Excel but it will
also allow you to (for example) cross join region and country attributes (if
region and country are within the same geography dimension) which you could
not do before. As for the way the results are shown, exactly the same -
heck I had written some ADOMD code back in 1999 (when it was still the
msolap driver) and simply changed the connection string to msolap.3 driver
and it returned the results without any problem.

--
HTH!
Denny Lee
<dennyglee_at_hotmail_dot_com>

Blog at:: http://spaces.msn.com/members/denster/



"Jimmy" <NoSpam> wrote

Thanks for you help.

"Denny Lee" <dennyglee (AT) hotmail (DOT) com> wrote