Using BIDS, after the DSV is developed, the
next step is to create dimensions. Dimensions are of two types:
Database Dimensions and Cube Dimensions. Database dimensions can be perceived
as a master template, and Cube dimensions can be perceived as instances /
children of this master template.
We will start our development with the creation of database dimensions. If you consider a dimension as a table, all the fields in this table can be perceived as attributes. Hierarchy in a dimension is a group of attributes logically related to each other with a defined cardinality. Finally we will create a cube using the dimensions we just developed, and fact tables to create dimensions (cube dimensions) and measure groups (from fact tables).
Cube Structure :Use this tab to create and modify measure groups and measures, add cube dimensions, and display the objects included in the cube from the associated data source view.
Dimension Usage:Use this tab to create and modify relationships between cube dimensions and measure groups included in the cube.
Calculations:Use this tab to create and modify calculations, including calculated members, named sets, and Multidimensional Expressions (MDX) scripts, included in the cube.
KPIs:Use this tab to create and modify KPIs included in the cube.
Actions:Use this tab to create and modify actions, including drillthrough actions and report actions, included in the cube.
Partitions:Use this tab to create and modify partitions, including proactive caching settings for measure groups and partitions, included in the cube.
Perspectives:Use this tab to create and modify perspectives included in the cube.
Translations: Use this tab to create and modify translations for measure groups, measures, cube dimensions, perspectives, KPIs, actions, named sets, and calculated members included in the cube.
Browser:Use this tab to browse data and metadata for the cube.
We will start our development with the creation of database dimensions. If you consider a dimension as a table, all the fields in this table can be perceived as attributes. Hierarchy in a dimension is a group of attributes logically related to each other with a defined cardinality. Finally we will create a cube using the dimensions we just developed, and fact tables to create dimensions (cube dimensions) and measure groups (from fact tables).
Use Cube Designer in SQL Server Data Tools
(SSDT) to edit various properties of an existing cube, including the measure
groups and measures, cube dimensions and dimension relationships, calculations,
key performance indicators (KPIs), actions, partitions, perspectives, and
translations included in the cube, as well as to browse the data contained by
the cube.
You can display the Cube Designer dialog box by:
- Right-clicking a cube in Solution Explorer and selecting Open or View Designer from the context menu.
- Double-clicking a cube in Solution Explorer.
- The Cube Designer contains the following tabs:
Cube Structure :Use this tab to create and modify measure groups and measures, add cube dimensions, and display the objects included in the cube from the associated data source view.
Dimension Usage:Use this tab to create and modify relationships between cube dimensions and measure groups included in the cube.
Calculations:Use this tab to create and modify calculations, including calculated members, named sets, and Multidimensional Expressions (MDX) scripts, included in the cube.
KPIs:Use this tab to create and modify KPIs included in the cube.
Actions:Use this tab to create and modify actions, including drillthrough actions and report actions, included in the cube.
Partitions:Use this tab to create and modify partitions, including proactive caching settings for measure groups and partitions, included in the cube.
Perspectives:Use this tab to create and modify perspectives included in the cube.
Translations: Use this tab to create and modify translations for measure groups, measures, cube dimensions, perspectives, KPIs, actions, named sets, and calculated members included in the cube.
Browser:Use this tab to browse data and metadata for the cube.
No comments:
Post a Comment