|
|
|
|
|
An operator that is
used to combine tuples to construct sets. For example:
{[time].[all
time].[2001].[january],
[time].[all time].
[2001].[February],[time].
[all time].[2001].[march]},or to combine members
to construct tuples such as ([Time].[January 2001],
[Geography].[U.S.A]) |
|
|
An operator that is
used in part to construct sets and tuples. It replaces a series of
comma operators. For example:
{[Time].[all Time].[2001].[January]
:
[Time].[all Time].[2001].[March]} |
|
|
The SET constructor
operator.
|
|
|
The alternative for
CrossJoin. If you use a single operator, it is a direct replacement.
You can nest CrossJoins by stringing additional operators and sets.
For example, these expressions are equivalent:
A * B – CrossJoin(
A, B )
A * B * C – CrossJoin
(A, CrossJoin( B, C ) )
|
+ (plus operator for
sets)
|
An alternative to union().
|
+ (plus operator for
strings)
|
A concatenation of two
strings.
|
|
|
Cause the OLAP server
to ignore anything between the initial token and final token. These
comments can span lines. NOTE: these comments do NOT nest.
|
|
|
Cause the OLAP server
to ignore anything after the double slash until the end of the line.
These comments can NOT span lines.
|
|
|
Cause the OLAP server
to ignore anything after the double dash until the end of the line.
These comments can NOT span lines.
These are essentially
the same as the double-slash comments.
|
|
|
When applied to an
axis, causes the OLAP Server to post-process the results of the axis
set and remove any tuples which have empty results.
For the SAS OLAP Server,
it works with CrossJoin to provide "Optimize NON EMPTY CrossJoin"
performance improvements.
|
|
|
Creates an alias for
an intermediate set. An intermediate set is one which is generated
during the evaluation of an axis and has one or more functions operating
on it.
|
|
|
TRUE and FALSE conditional
operators are supported in MDX queries
|
|
|
Executes a void returning
user-defined function.
|
|
|
Limits the size of sets
that the OLAP server creates. A value of 0 indicates there is no limit.
The default is 1,000,000 components, where components are defined
as the number of tuples in the set times the number of dimensions
in each tuple. This function enables the administrator to control
the system resources that are used by individual queries.
|