This value specifies the connection to use when deploying a cube.
Specifies the name of the object. This name can be used to reference this object from anywhere else in the program.
This value provides a common prefix for aggregation names used throughout the associated cube.
This value specifies how data is sorted and compared.
This value displays the current cube state with respect to processing.
Defines the name to use for the generated SSAS database.
This value contains a reference to the measure that should be used by the client application for the cube when a measure or measure group has not been specified in the query.
This value indicates the estimated number of items in the cube. The default setting is zero. This value is used to assist in aggregation design choices and other internal operations. While EstimatedCount can be set manually to reflect estimated member counts, BimlStudio also provides an automatic Member Count Estimator in the Cube ribbon.
This value specifies the language that is associated with the cube by default.
Specifies a path that should be used for organizing the tree display of this object in the Logical View in BimlStudio.
Specifies the name that should be used for this cube when it is emitted into the SSAS cube file. This name will be used both for the cube and the name of the cube file. If no OutputCubeLabel is specified, the Name property of this cube will be used in its place. Note that an OutputCubeLabel setting in a cube project referencing this cube can override the Name and OutputCubeLabel specified here. This property is provided to offer more fine-grained control over cube naming in automation scenarios, especially in multi-tenant environments. This can be important, since cube names are end-user visible.
This value specifies when indexing and aggregating should be performed. The options are Regular, which means that indexing and aggregations occur during processing, or Lazy, which means that indexing aggregation occur after after processing is completed.
This value specifies the priority of background processing operations relative to query handling, other non-background functions, and other functions that have a priority specified. Lower integer values indicate lower priority. The default value is 0.
This value specifies when the script cache is built. The options are Regular, which means that the cache is built during processing, or Lazy, which means that the script cache is built after processing is completed.
This value specifies how script errors are handled. The options are IgnoreNone, which means that the server generates an error whenever any MDX script error is encountered, and IgnoreAll, which means that the server ignores all MDX script errors.
This value specifies the full path where the cube’s files are located. If this value is not specified, then the storage location comes from the cube’s database information.
This value specifies which storage mode the cube will use.
The value specifies whether the cube is visible to end users. If it is not visible, the cube still exists on the server and can respond to queries, but it is not visible to end-users for browsing through the client application.
|<ErrorConfiguration />||AstErrorConfigurationNode||The AstErrorConfigurationNode type defines how the SQL Server Analysis Services engine will respond to various potential error conditions while processing objects in the cube.|
|<ProactiveCaching />||AstProactiveCachingNode||The AstProactiveCachingNodecorresponds directly to a proactive caching configuration definition in SQL Server Analysis Services.|
This defines a collection of actions that are associated with the cube. Actions are stored Multidimensional Expressions (MDX) statements that are associated with the cube. Client applications such as Microsoft Excel display actions to the end user and execute them against the cube when requested. Actions can include custom report generation, redirection to URLs, drillthrough to row details for a given cell, and other operations.
This is a collection of annotation items that can be used to specify documentation, tags, or other information. Annotations are particularly useful for storing information about nodes that can be used by BimlScript code.
This collection is used to define instances of dimensions that are used in the cube. Each dimension might be referenced by multiple cube dimensions in cases where a single dimension might be used in multiple ways. For example, a date dimension might be used to indicate purchase date, ship date, and received date for a sales-tracking cube.
This collection is used to define instances of fact tables that are used in the cube as measure groups. Each fact table might be referenced by multiple cube measure groups in cases where a single fact table might be used in multiple ways. For example, a fact table that tracks customer activity might be used both in a sales and an account measure group for a sales-tracking cube.
This defines a collection of key performance indicator (KPI) calculations that are associated with the cube. KPIs are used to track goals, trends, and current status for values that are considered critical to the overall performance of the business. They are normally an important feature of dashboard-style reports.
This defines the collection of Multidimensional Expressions (MDX) scripts that are associated with the cube. MDX scripts can contain calculated members, named sets, and standalone script objects.
This is a collection of simplified subsets of cube features. Perspectives enable users to generate specialized, more focused views of the data. Cube filtering is limited to a simple included/excluded choice for each independent cube asset. Note that perspectives are available only for deployments that target SQL Server Enterprise Edition.
This value contains alternate language versions of measure groups, measures, cube dimension, perspectives, KPIs, actions, named sets, and calculated members associated with a dimension. These are used by client applications such as Microsoft Excel to show values for dimension metadata that are consistent with the language of the end-user.