Short note/Explain Multidimensional Data Model.

 Multidimensional Data Model

  • Multidimensional data model stores data in the form of the data cube. Mostly, data warehousing supports two or three-dimensional cubes.
  • A data cube allows data to be viewed in multiple dimensions. Dimensions are entities with respect to which an organization wants to keep records. For example in-store sales records, dimensions allow the store to keep track of things like monthly sales of items and the branches and locations.
  • A multidimensional database helps to provide data-related answers to complex business queries quickly and accurately.
  • Data warehouses and Online Analytical Processing (OLAP) tools are based on a multidimensional data model.OLAP in data warehousing enables users to view data from different angles and dimensions.
  • Data warehouses and OLAP tools are based on a multidimensional data model which views data in the form of a data cube. A data cube enables data to be modeled and viewed in multiple dimensions. It is defined by dimensions and facts.

Dimensions are the perspectives or entities with respect to which an organization wants to keep records. The sales data warehouse may keep records of the store’s sales with respect to the dimensions time, item, branch, and location. Each dimension may have a table associated with it, called a dimension table. This table further describes the dimensions. For example, a dimension table for an item may contain the attributes item name, brand, and type.

- Facts are numerical measures that are used to analyze the relationship between dimensions. Examples of facts for a sales data warehouse include dollars_sold (sales amount in dollars), units_sold (number of units sold), and amount_budgeted. The fact table contains the names of the facts, or measures, as well as keys to each of the related dimension tables.

Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Discuss classification or taxonomy of virtualization at different levels.

Pure Versus Partial EC