Hierarchy For A Dimension or Introducing Additional Dimensions. (Reverse of Roll-Up)
Hierarchy For A Dimension or Introducing Additional Dimensions. (Reverse of Roll-Up)
In the multidimensional model, data are organized into multiple dimensions, and each dimension
contains multiple levels of abstraction defined by concept hierarchies. The different OLAP
operations used are as follows
Roll-up: The roll-up operation (also called the drill-up operation by some vendors)
performs aggregation on a data cube, either by climbing up a concept hierarchy for a
dimension or by dimension reduction.(summarize data)
Drill-down: Drill-down is the reverse of roll-up. It navigates from less detailed data to
more detailed data. Drill-down can be realized by either stepping down a concept
hierarchy for a dimension or introducing additional dimensions.( reverse of roll-up)
Slice: The slice operation performs a selection on one dimension of the given cube,
resulting in a subcube. (project )
Dice: The dice operation defines a subcube by performing a selection on two or more
dimensions.(select)
Pivot (rotate): Pivot (also called rotate) is a visualization operation that rotates the data
axes in view in order to provide an alternative presentation of the data. (reorient the cube,
visualization, 3D to series of 2D planes)
Other OLAP operations:
The drill-across executes queries involving (i.e., across) more than one fact table.
The drill-through operation uses relational SQL facilities to drill through the
bottom level of a data cube down to its back-end relational tables.
2)Fact constellation: Sophisticated applications may require multiple fact tables to share
dimension tables. This kind of schema can be viewed as a collection of stars, and hence is called
a galaxy schema or a fact constellation.
Example: Fact constellation schema of a data warehouse for sales and shipping.
This schema specifies two fact tables, sales and shipping.
3)Snowflake schema: The snowflake schema is a variant of the star schema model, where some
dimension tables are normalized, thereby further splitting the data into additional tables. The
resulting schema graph forms a shape similar to a snowflake.
Example: Snow flake schema for the dimensions item, time and location.
----Figure2
Difference between the snowflake and star schema models is that
The dimension tables of the snowflake model may be kept in normalized form to reduce
redundancies. Such a table is easy to maintain and saves storage space.
The snowflake structure can reduce the effectiveness of browsing, since more joins will
be needed to execute a query.
Although the snowflake schema reduces redundancy, it is not as popular as the star
schema in data warehouse design.