This document uses the following terms:
action: An OLAP object, such as a cube, dimension, and cell, that has an action associated with it, so that a user can perform that action when browsing OLAP data. For example, a user can jump to a URL, execute a command, or drill through to data.
assembly: A managed application module that contains class metadata and managed code as an object in Microsoft SQL Server, against which common language runtime (CLR) functions, stored procedures, triggers, user-defined aggregates, and user-defined types can be created in SQL Server.
attribute hierarchy: An implied single-level hierarchy, based on a single attribute, that consists of all the members of the attribute. An all-level member can optionally be enabled for an attribute hierarchy.
complex type: An element that can contain other elements or attributes and appears as <complexType> in an XML document. See also simple type.
Component Object Model (COM): An object-oriented programming model that defines how objects interact within a single process or between processes. In COM, clients have access to an object through interfaces implemented on the object. For more information, see [MS-DCOM].
cube: A set of data that is organized and summarized into a multidimensional structure that is defined by a set of dimensions and measures.
data block: A unit of data that is transferred at one time between an application and an instance of Microsoft SQL Server Analysis Services. The term is also applied to the units of storage for these data types.
data definition language (DDL): A subset of SQL or XMLA statements that defines all the attributes and properties of a database and its objects. DDL statements typically begin with CREATE, ALTER, or DROP.
data mining dimension: A dimension that is specified when the MiningModel ID element for a dimension is non-empty. Certain other restrictions apply to the dimension's definition beyond what can be expressed in XSD.
lazy aggregation: An aggregation that is rebuilt by the server in the background after the processing step has been completed, instead of during the processing step. This is the process that underlies expressions, such as partitions that are "lazily processed," and aggregations and indexes that are "built lazily."
locale ID: See language code identifier (LCID).
mining structure: A data mining object that defines the data domain from which the mining models are built.
MOLAP: A memory model in which multidimensional data aggregates are stored on disk (Multidimensional OLAP).
Multipurpose Internet Mail Extensions (MIME): A set of extensions that redefines and expands support for various types of content in email messages, as described in [RFC2045], [RFC2046], and [RFC2047].
Online Analytical Processing (OLAP): A technology that uses multidimensional structures to provide access to data for analysis. The source data for OLAP is stored in data warehouses in a relational database. See also cube.
partition: One of the storage containers for data and aggregations of a cube. Every cube contains one or more partitions. For a cube with multiple partitions, each partition can be stored separately in a different physical location. Each partition can be based on a different data source. Partitions are not visible to users; the cube appears to be a single object.
proactive caching: A system that manages data obsolescence in a cube by which objects in MOLAP storage are automatically updated and processed in the cache, while queries are redirected to ROLAP storage.
remote partition: A partition whose data is stored on a server that is running an instance of Analysis Services other than the one used to store the metadata of the partition.
repeated base: A base column where the trace provider can reference previous data and therefore omit resending a column to SQL Server Profiler. The client tool keeps track of all repeatable columns for each new repeated-base column value.
ROLAP: A memory model in which no multidimensional aggregates are stored, and in which the server must make a relational query to obtain an aggregate upon the request of an individual query (Relational OLAP).
simple type: An element that can contain only text and appears as <simpleType> in an XML document or any attribute of an element. Attributes are considered simple types because they contain only text. See also complex type.
slicer axis: A filter for the data that is returned by a multidimensional expression (MDX) SELECT statement. The slicer axis restricts the returned data so that only data that intersects with specified members is returned. It can be thought of as an invisible extra axis in a query. The slicer axis is defined in the WHERE clause of the SELECT statement.
SOAP fault: A container for error and status information within a SOAP message. See [SOAP1.2-1/2007] section 5.4 for more information.
SOAP header: A mechanism for implementing extensions to a SOAP message in a decentralized manner without prior agreement between the communicating parties. See [SOAP1.2-1/2007] section 5.2 for more information.
tuple: An ordered grouping of members from different dimensions or hierarchies. A single member is a special case of a tuple and can be used as an expression. Every hierarchy does not have to be represented in a tuple.
unbalanced hierarchy: A hierarchy in which one or more levels do not contain members in one or more branches of the hierarchy. This is also known as a ragged hierarchy.
Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].
WSDL message: An abstract, typed definition of the data that is communicated during a WSDL operation [WSDL]. Also, an element that describes the data being exchanged between web service providers and clients.
XML namespace: A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference [RFC3986]. A combination of XML namespace and local name allows XML documents to use elements, types, and attributes that have the same names but come from different sources. For more information, see [XMLNS-2ED].
XML Schema (XSD): A language that defines the elements, attributes, namespaces, and data types for XML documents as defined by [XMLSCHEMA1/2] and [W3C-XSD] standards. An XML schema uses XML syntax for its language.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.