hi,

go for microsoft olap unleashed. it will discuss in detail
abt all these.

and one more good book is MDX Solutions.

u can know all abt these things in help menu of MDX or
books online.

And another *excellent* source is "Fast Track to MDX" at:
http://search.barnesandnoble.com/boo...SBN=1852336811
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"alex" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Hi

Specifically, you can find good stuff online at the following URLs:

http://msdn.microsoft.com/library/de...asics_3md4.asp
and
http://www.microsoft.com/downloads/d...displaylang=en

And to try and put it simple (examples are based on the Foodmart 2000 sample
database):

Members are occurences along the dimension's hierarchies (ex:
[Customers].[Country].[USA], [Time].[1997].[Q1], [Measures].[Unit Sales])
Members can be used in MDX expressions as individual coordinates for the
cubes' cells.
Members are referenced in MDX using a fully-qualified name based on the
dimension and hierarchy they belong to, their ancestors, etc. (notice the
square brackets [] surrounding names).
Members are grouped in levels within the hierarchies.

Levels are groups of individual members with the same granularity (ex: the
[Product].[Product Family] level contains all product families, e.g. the
following members: [Product].[All Products].[Drink], [Product].[All
Products].[Food] and [Product].[All Products].[Non-consumable].
Levels contain members but they are not members themselves (rather
categories of members).
Levels are defined when creating the dimension's hierarchies and cannot be
changed afterwards without breaking the cubes (in general).
Levels can be used in MDX as arguments of functions that deal with
collections (or sets) of members (ex: the .Members function takes a level
name as argument and returns all individual members found in the level).

Sets are basically collections of members of a given dimension/hierarchy
(ex: { Product].[All Products].[Drink], [Product].[All Products].[Food],
[Product].[All Products].[Non-consumable] } is the set of all members found
in the [Product].[Product Family] level ; notice the curly braces {}
surrounding any set expression).
Sets can contain duplicate members as well as members from any level as long
as they come from the same hierarchy.
Sets are typically used in MDX whenever you need to deal with collections of
members in an iterative manner (ex: you use sets on the rows/columns of an
MDX query to display a report; you can also use sets as an argument in an
agregation functions such as Sum()).
Sets can also be more complex and contain tuples instead of members.

Tuples represent the set of coordinates for an dividual cells in a cube.
Tuples are made up of one single member from each dimension/hierarchy in a
cube, including the Measures dimension (ex: ([Account].[All
Account].[Assets],[Category].[All
Category].[Forecast],[Measures].[Amount],[Store].[All
Stores].[USA],[Time].[1997]) defines with no ambiguity a single cell from
the Budget cube ; notice the parens () around each Tuple expression).
Tuples can contain members from any member from any level from any hierarchy
in the cube, in any order, as long as each member comes from a different
herarchy within a given tuple.
Tuples can be complete (when one member exactly is specified for every
single hierarchy in the cube) or partial (when they contain no member for
some hierarchies; in that case the current member is assumed for each
missing hierarchy in order to figure out a complete tuple).
Tuples with the same number of members in the same order can be used instead
of members in Sets definitions.


HTH

Olivier MATRAT

WINSIGHT
Microsoft Gold Certified Partner for Business Intelligence
www.winsight.fr
www.olapwebhouse.com




"Stanley" <Stanley (AT) discussions (DOT) microsoft.com> wrote

Hi

Specifically, you can find good stuff online at the following URLs:

http://msdn.microsoft.com/library/de...asics_3md4.asp
and
http://www.microsoft.com/downloads/d...displaylang=en

And to try and put it simple (examples are based on the Foodmart 2000 sample
database):

Members are occurences along the dimension's hierarchies (ex:
[Customers].[Country].[USA], [Time].[1997].[Q1], [Measures].[Unit Sales])
Members can be used in MDX expressions as individual coordinates for the
cubes' cells.
Members are referenced in MDX using a fully-qualified name based on the
dimension and hierarchy they belong to, their ancestors, etc. (notice the
square brackets [] surrounding names).
Members are grouped in levels within the hierarchies.

Levels are groups of individual members with the same granularity (ex: the
[Product].[Product Family] level contains all product families, e.g. the
following members: [Product].[All Products].[Drink], [Product].[All
Products].[Food] and [Product].[All Products].[Non-consumable].
Levels contain members but they are not members themselves (rather
categories of members).
Levels are defined when creating the dimension's hierarchies and cannot be
changed afterwards without breaking the cubes (in general).
Levels can be used in MDX as arguments of functions that deal with
collections (or sets) of members (ex: the .Members function takes a level
name as argument and returns all individual members found in the level).

Sets are basically collections of members of a given dimension/hierarchy
(ex: { Product].[All Products].[Drink], [Product].[All Products].[Food],
[Product].[All Products].[Non-consumable] } is the set of all members found
in the [Product].[Product Family] level ; notice the curly braces {}
surrounding any set expression).
Sets can contain duplicate members as well as members from any level as long
as they come from the same hierarchy.
Sets are typically used in MDX whenever you need to deal with collections of
members in an iterative manner (ex: you use sets on the rows/columns of an
MDX query to display a report; you can also use sets as an argument in an
agregation functions such as Sum()).
Sets can also be more complex and contain tuples instead of members.

Tuples represent the set of coordinates for an dividual cells in a cube.
Tuples are made up of one single member from each dimension/hierarchy in a
cube, including the Measures dimension (ex: ([Account].[All
Account].[Assets],[Category].[All
Category].[Forecast],[Measures].[Amount],[Store].[All
Stores].[USA],[Time].[1997]) defines with no ambiguity a single cell from
the Budget cube ; notice the parens () around each Tuple expression).
Tuples can contain members from any member from any level from any hierarchy
in the cube, in any order, as long as each member comes from a different
herarchy within a given tuple.
Tuples can be complete (when one member exactly is specified for every
single hierarchy in the cube) or partial (when they contain no member for
some hierarchies; in that case the current member is assumed for each
missing hierarchy in order to figure out a complete tuple).
Tuples with the same number of members in the same order can be used instead
of members in Sets definitions.


HTH

Olivier MATRAT

WINSIGHT
Microsoft Gold Certified Partner for Business Intelligence
www.winsight.fr
www.olapwebhouse.com




"Stanley" <Stanley (AT) discussions (DOT) microsoft.com> wrote

Thnx

"Olivier Matrat" wrote:

thnx

"Jamie" wrote: