The central metadata object in ADO MD is the cube, consisting of a structured set of related dimensions, hierarchies, levels, and members. Members can be consolidated or aggregated along one or more hierarchies per dimension, meaning that members can be totaled or "rolled up" in multiple ways.
Consider a Sales Data cube with six dimensions: Salesperson, Geography, Quarters, Years, Measures, and Products. The Geography dimension has the following set of members (only two continents are used for the sake of simplicity):
{All, North America, Europe, Canada, USA, UK, Germany, Canada-West, Canada-East, USA-NW, USA-SW, USA-NE, USA-SE, England, Scotland, Wales, Ireland, Germany-North, Germany-South, Ottawa, Toronto, Vancouver, Calgary, Seattle, Boise, Los Angeles, Houston, Shreveport, Miami, Boston, New York, London, Dover, Glasgow, Edinburgh, Cardiff, Pembroke, Belfast, Londonderry, Berlin, Hamburg, Munich, Stuttgart}
A natural hierarchy exists in this dimension:
The World | |||||||
Continents | |||||||
Countries | |||||||
Regions | |||||||
Cities |
Each box is a level in the hierarchy. Each level has a set of members, as follows:
Members at the leaf level have no children, and member at the root level have no parents. All other members have at least one parent and at least one child. For example, a partial traversal of the hierarchy tree in the Geography dimension yields the following parent-child relationships:
Multiple simultaneous hierarchies (multiple aggregation paths) are often useful. Consider the Time dimension of the Sales Data cube. There are two ways to roll up to the Year level from the Days level:
Year | Year |
Quarter | Week |
Month | Day of Week |
Day of Month |
This example also illustrates another characteristic: Some members of the Week level of the Year-Week hierarchy do not appear in any level of the Year-Quarter hierarchy. Thus, a hierarchy need not include all members of a dimension.