Chapter 14 DBMS-Specific Features


Comparing PowerDesigner and DSO metamodels

Conceptually, DSO uses hierarchically arranged groups of objects to define basic elements of Analysis Services data storage, as implemented by the Analysis server. These basic elements are databases, data sources, dimensions, cubes, data mining models, and roles.

DSO maintains these basic elements in a hierarchical structure where elements contain other elements in a tree, with the server object at the root of the tree. Other objects support this basic structure. For example, databases, cubes, partitions, and aggregations support dimensions.


PowerDesigner and DSO have a different metamodel. The following table maps PowerDesigner to DSO objects.

PowerDesigner object
DSO object

Comment
Model clsDatabase Each model corresponds to a DSO Database.
Data source clsDataSource  
Dimension ClsDatabaseDimension Like DSO Database Dimension, PowerDesigner dimensions are shared among cubes.
Cube clsCube Cubes managed by PowerDesigner are only local cubes.
Fact clsCube A Fact corresponds to a DSO cube in order to store measures.
Measure clsCubeMeasure  
Dimension hierarchy clsDatabaseDimension Each dimension hierarchy is generated as a DSO Database Dimension. Attributes of a dimension hierarchy define levels of the corresponding DatabaseDimension.
Dimension attribute clsDatabaseLevel
clsCubeLevel
Attributes of a dimension or dimension hierarchy define levels in a database dimension.
Cube dimension association clsCubeDimension A dimension association is defined by a DSO Cube Dimension. In DSO, when the name of a Cube Dimension corresponds to the name of a Database Dimension, the Cube Dimension is automatically associated with the Database Dimension to be shared between cubes.

 


Copyright (C) 2005. Sybase Inc. All rights reserved.