Building Making It Happen
Establishing Making-it-Happen as ‘Formal & Measurable’ Business Discipline
  Sign-in         Register
    
  Dimensional Model Schemas- Star, Snow-Flake and Constellation  

Execution-MiH Encyclopedia  →   Enterprise Intelligence  →  SECTION -  Data-Warehouse/Mart  →  CHAPTER -  DW Dimensional Modeling Concepts  → 

Data Warehouse Dimensional Model Components Concept

Dimensional model is equivalent of logical data design of Data Warehouse, and much more. It is more simplistic in design and suits the purpose of a data warehouse.

Dimensional Modeling Concept

Dimensional Model is a logical design technique that seeks to present the data in a standard, intuitive framework that allows for high-performance access. It is inherently dimensional, and it adheres to a discipline that uses the relational model with some important restrictions. Every dimensional model is composed of one table with a multi-part key, called the fact table, and a set of smaller tables called dimension tables. Each dimension table has a single-part primary key that corresponds exactly to one of the components of the multi-part key in the fact table. (See Figure) This characteristic 'star-like' structure is often called a star join.

A fact table, because it has a multi-part primary key made up of two OR more foreign keys, always expresses a many-to-many relationship. The most useful fact tables also contain one OR more numerical measures, OR 'facts,' that occur for the combination of keys that define each record. In Figure, the facts are Units_Sold, Dollars_Sold, and Avg_sales. The most useful facts in a fact table are numeric and additive. Additivity is crucial because data warehouse applications almost never retrieve a single fact table record; rather, they fetch back hundreds, thousands, OR even millions of these records at a time, and the only useful thing to do with so many records is to add them up.

Dimension tables, by contrast, most often contain descriptive textual information, and the attributes (also called classification attributes), which are used for analysis. Dimension attributes are used as the source of most of the interesting constraints in data warehouse queries, and they are virtually always the source of the row headers in the SQL answer set.

Fact Table and Dimension Tables in a Dimensional Model Schema

Lets consider a Data-Warehouse cube. This cube has 4 dimensions and three measures. This means that for every value of each of these 4 dimensions there will two values of coordinates. For example:

Co-ordinate [City(X), Product(Y), channel(Z),Month] = [ Sales (Quantity), Sales (Value)]
OR [NY, Standard Desk-top, Mail, September 2005] = [2000 units, $15000]

In the dimensional modeling schema, the FACT table contains the value of coordinates against the lowest granularity of all the possible combinations of dimensions. The dimension tables contain the details of the dimensions, which include the attributes of dimensions including all the higher-level hierarchies. The link between the fact table and all the associated dimension tables is through a dimension key, which is the lowest level granularity primary key of the dimension tables.

Fact Table- The central linkage in Dimensional Modeling

A fact table contains the value of all the measures linked to the set of dimensions linked to the FACT table. It contains the measure values for the combination of lowest level of granularity of dimensions. The measures are typically numeric, which can undergo mathematical aggregation and analysis.

Families of FACT Tables

  • Chains and Circles.
  • Heterogeneous products.
  • Transactions and snapshots.
  • Aggregates


Dimension Table- What does and should it contain

The dimension table contains all the information on the dimension. This includes:

a. The primary key (Equivalent foreign key in the Fact Table).

b. All attributes of the dimension. These include:

  • The hierarchy attributes- Consider a business hierarchy-- pin-code to city to district to state to country for location dimension. This means that each hierarchy element will be an attribute.
  • Textual as well as the code attributes- Location code as well as the name of the location. This is required, because both could be used for different reasons by different users. A power user could be looking for location code (NY01), whereas an end user could be looking for more explicit header (New Jersey).
  • Include all parallel hierarchies – A product could be having different hierarchies, depending upon if CFO OR Head of sales is looking at it. This enables the done on all hierarchies as well as cross-hierarchies.
  • Production Primary Key Refer Surrogate primary key link to FACT table– These keys are used because the production keys could change OR could be reused. For example a bill number could be reused after 5 years, OR a part number (especially FMCG) could be reused after few years.
  • Production OR source system key- This is required for audit ability OR link to the Extraction data and source systems.
 

  Dimensional Model Schemas- Star, Snow-Flake and Constellation  
 
All Topics in: "DW Dimensional Modeling Concepts" Chapter
 Data Warehouse Dimensional Model Components Concept →  Dimensional Model Schemas- Star, Snow-Flake and Constellation →  Dimensional Modeling vs. Relational Modeling →  Foundation & Conformed Dimensions and Facts in Data Warehouse Dimensional Model →  Slowly Changing Dimensions SCD in Dimensional Modeling → 
 
Relevant Links to this page
Practice Tools → Dimensional Model Completion Checklist → 

Was this page helpful?
If you like it ? share it !
Digg
Digg
Reddit
Reddit
Del.icio.us
Delicious
Google
Google
Live
Live
Facebook
Facebook
Slashdot
Slashdot
Netscape
Netscape
Technorati
Technorati
Stumbleupon
Stumbleupon
Spurl
Spurl
Furl
Furl
Blogmarks
Blogmarks
Yahoo
Yahoo
Plugim
Plugim
Squidoo
Squidoo
BlinkBits
BlinkBits
 
CONTENT ZONE
Data-Warehouse/Mart

Featured Pages
Business process based data-marts
Dimensional Model Simple Hierarchy
Data Quality Gaps Management Tool
Derived Dimension Attributes Table

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
Data Mining Technology
Customer Data Correction and Techniques
BI Mixed Data Access
Single & Stable system for Data Marts