Data Values

The intersection of one member from one dimension with one member from each of the other dimensions represents a data value. The example in Figure 16, Three-Dimensional Database has three dimensions (Accounts, Time, and Scenario); therefore, the dimensions and data values in the database can be represented as a cube.

Figure 16. Three-Dimensional Database

This image illustrates a three-dimensional database as a cube, as described in the text preceding the image.

As illustrated in Figure 17, Sales Slice of the Database, when you specify Sales, you are specifying the slice of the database that contains eight Sales values, where Sales intersect with Actual and Budget.

Figure 17. Sales Slice of the Database

This image illustrates a slice of data in the cube, as described in the text preceding the image.

Slicing a database amounts to fixing one or more dimensions at a constant value while allowing the other dimensions to vary.

As illustrated in Figure 18, Actual, Sales Slice of the Database, when you specify Actual Sales, you are specifying the slice of the database that contains four Sales values, where Actual and Sales intersect.

Figure 18. Actual, Sales Slice of the Database

This image illustrates a slice of data in the cube, as described in the text preceding the image.

A data value is stored in one cell in the database. To refer to a specific data value in a multidimensional database, you specify its member on each dimension. In Figure 19, Sales->Jan->Actual Slice of the Database, the cell containing the data value for Sales, Jan, Actual is shaded. The data value can also be expressed using the cross-dimensional operator (->) as Sales -> Actual -> Jan.

Figure 19. Sales->Jan->Actual Slice of the Database

This image illustrates a slice of data in the cube, as described in the text preceding the image.