Relational Cube Editor

The third relational database connection wizard panel, Relational Cube Editor, diagrams the relational cube as a node tree.

Default Node

Shortcut Menu

Right-click node and select menu command to:

Relational Cube

  
 

Rename Cube

Specifies the relational database connection name.

Dimensions

  
 

Add Dimension

Creates a dimension.

Defined Dimension

  
 

Add Generation

Specifies a relational column as a dimension generation.

 

Rename Dimension

Specifies a name for the dimension.

 

Delete Dimension

Removes the dimension from the node hierarchy.

 

Preview

Displays a node tree of the selected dimension hierarchy.

Defined Generation

  
 

Edit Generation

Changes properties for that generation.

 

Rename Generation

Specifies a name for that generation.

 

Delete Generation

Removes that generation from the node hierarchy.

 

Move Up

Moves that generation up in the node hierarchy.

 

Move Down

Moves that generation down in the node hierarchy.

 

Preview

Displays a node tree of the selected dimension hierarchy.

Measures

  
 

Edit Measures

Specifies columns as measures.

 

Rename

Specifies another name for the measures dimension.

 

Preview

Displays a node tree of the selected dimension hierarchy.

Defined Measure

  
 

Rename Member

Specifies a name for the measure.

 

Delete Measure

Removes the measure from the node hierarchy.

 

Preview

Displays a node tree of the selected dimension hierarchy.

 

Order By Mode

Indicates the label used to determine Dimension Header Sorting. Options include ID and Alias.

 

Dimension Header Sort

Indicates the order that relational members are displayed by the Dimension Browser dialog box. Subsequent users must use this dialog box to select members from the relational data source. Options include:

  • Default (Natural ordering based on outline)

  • Ascending

  • Descending

Properties

 

Displays the properties of the currently selected node.

Important notes on relational table properties:

To protect open documents and to expedite network traffic, there is only one cached JDBC connection per user per relational database connection. Therefore, relational database connection edits are not implemented until you log off Web Analysis Studio and log back on.