The properties associated with a cube are described below. These properties relate both to the cube environment and to the cube itself.
There are seven tabs in the cube Properties screen. The first is the main properties, the second the processing and partitioning options and the rest are for documentation stored in the WhereScape RED metadata and displayed in the generated WhereScape RED documentation.
In order to see the cube properties, right-click the cube name and then select Properties.

Fields

Description

Internal Cube Name

This is the name by which the cube is known within WhereScape RED. This name is limited to 64 characters in length and may contain only alphanumeric characters and underscores.

Cube Publish Name

This is the name of the cube in the Analysis Services server. It is not constrained in its content except for the limitations imposed on it by Analysis Services.

Cube Description

A description of the cube. This is used both in the WhereScape RED documentation and is also stored against the cube in Analysis Services.

Cube Database Connection

This field enables the selection of one of the existing connections defined within WhereScape RED. The connection must be of type 'Microsoft Analysis Server 2005+'. If no such connection exists then a new connection object must be created. This connection object is used to point to the Analysis Services server.

Cube Database Name

An Analysis Services server must have databases associated with it. Each database can contain one or more cubes, dimensions, data sources etc. Select the name of an existing database on the server from the drop-down list. To create a new Database name, select (Define New Cube Database) from the drop-down list and the displayed window enables you to register the name within the WhereScape RED metadata. Once registered, the name can then be selected as the database.

Data Source Connection

In Analysis Services the data source is the location of the data to be used to build the cube. It also defines the path for any drill through operations. This field provides a drop-down of the existing connections. The Data Warehouse connection must be chosen.

Data Source Provider Type

This field essentially defines what type of database the Data Warehouse is. The three options are:
· MSDAORA where the data source is an Oracle database
· OLESQLDB where the data source is a SQL Server database, or
· MSDASQL to define an ODBC source
The MSDASQL provider type could be used for either Oracle or SQL Server data warehouses, but performance may be compromised. This field is Read-Only in the Properties screen. Its value is set in the properties of the data source connection.

Data Source Server

The data source server is also a read only field being sourced from the properties of the data source connection. For SQL Server, it defines the server on which the data warehouse database runs. For Oracle, it is the TNS names entry for the database.

Data Source Database

The data source database is also a read only field being sourced from the properties of the data source connection. For SQL Server, it defines the database in which the data warehouse runs. For Oracle, it is also the database name.

Post Create XML/A Script

This is an XML/A script that is run on the cube database when the cube is created. This script enables Analysis Services features to be added to the cube or cube database that have been built outside of WhereScape RED—for example security roles that have been defined for the cube can be recreated from the script, when the cube is created (or recreated).

Post Update XML/A Script

This is an XML/A script that is run on the cube database, when the cube is updated or processed via the scheduler. This script enables Analysis Services features to be added to the cube or cube database that have been built outside of WhereScape RED—for example security roles that have been defined for the cube can be recreated from the script when the cube is updated or processed.

Processing Mode

Gets or sets the index and aggregation settings for cube processing. The value indicates whether processed data is available after all required data aggregation has been completed (Regular) or immediately after the data has been loaded (Lazy Aggregations). This setting is used as the default for new measure groups and partitions created for the cube.

Processing Priority

Gets or sets the processing priority for the cube.

Partition Processing Mode

This option determines how partitions are updated, when a cube is updated.
 
· All Partitions - Sequential updates each cube partition sequentially.
· All Partitions - Parallel all the cube partitions are updated in parallel.
· Measure Group Partitions - Parallel processes each measure group sequentially with all partitions of that same measure group being updated in parallel.

Process Cube Dimensions

Determines whether to process the OLAP Dimensions related to the cube, as part of the processing of the cube. The options are to process the enabled dimensions only, to process no dimensions, or to process all the dimensions.Processing of specific Dimensions with the Cube can be enabled or deactivated via the Process Cube Dimension With Cube check box of each Dimension's Properties screen. Refer to OLAP Cube Dimensions for details.

Process Selected Cube Dimensions in Parallel

Select this check box to enable all dimensions within the cube to be updated in parallel, instead of being updated sequentially.

Storage Mode

This field enables two options; MOLAP (Multidimensional OLAP) or ROLAP (Relational OLAP). At the cube properties level, setting this field determines the defaults for the Storage Mode field, on its related Measure Groups and partitions.

Default Measure

Specifies the measure used to resolve MDX expressions if a measure is not explicitly referenced in the expression. If no default measure is specified an arbitrary measure is used as the default measure.

Estimated Rows

Specifies the estimated number of rows in the Fact tables. Enter the size of the fact or source table if known, otherwise leave as zero.

Visible

Indicates whether the cube is visible to client applications.
· ROLAP stands for Relational Online Analytical Processing.
· ROLAP is an alternative to the MOLAP (Multidimensional OLAP) technology. While both ROLAP and MOLAP analytic tools are designed to allow analysis of data using  a multidimensional data model, ROLAP differs significantly in that it does not require the pre-computation and storage of information. Instead, ROLAP tools access the data in a relational database and generate SQL queries to calculate information at the appropriate level when an end user requests it. With ROLAP, it is possible to create additional database tables (summary tables or aggregations) which summarize the data at any desired combination of dimensions.
· While ROLAP uses a relational database source, generally the database must be carefully designed for ROLAP use. A database which was designed for OLTP will not function well as a ROLAP database. Therefore, ROLAP still involves creating an additional copy of the data. However, since it is a database, a variety of technologies can be used to populate the database.

Language Mapping

The OLAP Cube Properties screen has a tab called Language Mapping.
Select the language from the drop-down list and then enter the translations for the Cube Publish Name and the CubeDescription in the chosen language.
 
Refer to Language Options for details on how to add languages for translation.

  • No labels