CellSet.Axes Property

Gets an instance of the AxisCollection class that contains the axes of the CellSet.

Namespace:   Microsoft.AnalysisServices.AdomdClient
Assembly:  Microsoft.AnalysisServices.AdomdClient (in Microsoft.AnalysisServices.AdomdClient.dll)

Syntax

public AxisCollection Axes { get; }

public:
property AxisCollection^ Axes {
    AxisCollection^ get();
}

member Axes : AxisCollection with get

Public ReadOnly Property Axes As AxisCollection

Property Value

Type: Microsoft.AnalysisServices.AdomdClient.AxisCollection

An AxisCollection that contains the axes of the CellSet.

Remarks

In Analysis Services, the data represented by a cellset is organized along one or more axes. To visually organize this information, the CellSet supplies an Axis for each query axis. These objects are available within an AxisCollection collection that the Axes property provides.

Filter and Query Axes

A typical MDX SELECT statement defines one or more axes for which data is displayed. These are called query axes. For example, the following MDX SELECT statement defines two query axes, COLUMNS and ROWS, in a query against the Adventure Works cube:

SELECT
   [Account].[Account].Children ON COLUMNS,
   [Reseller].[Reseller].Children ON ROWS
FROM
   [Adventure Works]

You might assume that this MDX query represents a cellset with two axes. In fact, three axes are represented — two query axes and a filter axis.

A filter axis filters multidimensional data in the same way as a query axis. However, a filter axis is always present in an MDX query, and unless defined otherwise, it consists of the default member of each hierarchy that is not explicitly referenced by a query axis. You can use the WHERE clause of an MDX SELECT statement to define a filter axis explicitly. For example, the following MDX query returns the same results as the previous MDX query, but the filter axis that was implied in the previous query is now more explicitly declared:

SELECT
   [Account].[Account].Children ON COLUMNS,
   [Reseller].[Reseller].Children ON ROWS
FROM
   [Adventure Works]
WHERE 
    ([Measures].DEFAULTMEMBER, [Date].[Calendar].DEFAULTMEMBER)

Another difference between a filter axis and a query axis is that a filter axis must resolve to a single tuple, whereas a query axis must resolve to a single set.

Because the filter axis is often implicitly included rather than explicitly declared in MDX queries, it is important to remember that a filter axis always exists. The filter axis is not included in the collection returned by this property; for zero-dimensional MDX queries, this property returns an empty collection. To retrieve the filter axis, use the FilterAxis property to retrieve a reference to an Axis that represents the filter axis.

See Also

CellSet Class
Microsoft.AnalysisServices.AdomdClient Namespace

Return to top