Sales Management Customer Relationship Human Resources Business Performance BI & Data Quality IT Tools & Vendors

Sign-in   Register
Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline
Principles and Rules Listing Page

Dimensional model has to be aligned to the Entity-Relationship

The cardinality of relationship between any two entities (refer entitiy relationship model ) have to be reflected equally in a dimensional model or else you will get an information management/business intelligence platform which is inconsistent with the organization data model
 
This page of 'Principles and Rules' is linked to:  Data Warehousing, Data Analysis/OLAP, BI platform Tools Evaluation, BI business intelligence end-to-end view, Metadata Management, Core Data Management Tools,

If there is many-to-many relationship between sales office and product sold as per the organization data model, a dimensional model cannot have one-to-many relationship for same dimensions.

If we do something like that, we may find data from the source system which cannot be fitted into dimensional model. For example- Let us say that you have one-to-many relationship between the product and product related discount packages. However, in the dimensional model, we have only one-on-one relationship between the product and product related discount package. You will find that dimensional model will stop accepting any further data after it has populated one product to product discount packages (because internal/table level checks will stop any further discount packages to be added for the same product). Similarly, if you try to have many-to-many products sold by the sales office (Any sales office can sell any products), to be represented as one-to-many (No sales office can sell the same product), you will be stuck, as the sales office dimensional table will not allow the same product to be added with another sales office.

As a side note-this kind of situation will be mostly encountered, when you are trying to have the relationship across two dimensions to be included in the same table.


Quick Feedback- Was this information helpful ?
Relevant Links to this page
TOPIC - Dimensional Modeling vs. Relational Modeling → Principles & Rules → Dimensional model has to be aligned to the Entity-Relationship → Principles & Rules → Always Use Conformed Dimensions → Principles & Rules → You may not be a able to have a perfect ETL → Practice Techniques → Handling Sparse Dimensional tables → Principles & Rules → Do not separate the parent and child line item data → Practice Techniques → Managing time-stamps across multiple time-zones → Practice Techniques → Recording events in multiple currencies → Practice Techniques → Handle different units of measure in the same fact table → Principles & Rules → Handling of Null foreign Keys in fact tables → Principles & Rules → Dimension Attributes as NULL → Principles & Rules → Don't rely too much on Meta Data Tools to enforce Business Intelligence → Principles & Rules → Don't wait for universal models for Data Marting → Principles & Rules → Add extra buffer for ETL phase → Principles & Rules → Homework before interviews is must (Business Requirements Phase in Data Warehouse) → Principles & Rules → Excel is the competition, which should be challenged → Principles & Rules → Avoid Pure MOLAP → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Consolidate Data-Marts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Licensing & Maintenance Contracts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Governance & Standards → Practice Techniques → Field Tips Series- Streamlining & reducing cost of Business Intelligence- Evaluate Open Source → Principles & Rules → Master Data Management- Making a Right Start → Practice Techniques → How to integrate stand-alone BI environments- Gradual Approach → Principles & Rules → Business owned applications are a reality- Manage it → Principles & Rules → New Data Standards- What about existing data and applications? → Principles & Rules → Handle Each Time-stamp in the Fact Table as a separate dimension → Principles & Rules → Keep Aggregates and Details data in different Fact tables → Principles & Rules → Some considerations for Infrastructure in Data Warehouse → Principles & Rules → For Core BI platform go for a single, established and robust player → Principles & Rules → Don't be guided only by the business requirements for your Business Intelligence → Practice Techniques → Using Synonyms and Views → 
 
Back
 
Relevant links to this page
Dimensional Modeling vs. Relational Modeling
Dimensional model has to be aligned to the Entity-Relationship
Always Use Conformed Dimensions
You may not be a able to have a perfect ETL
Handling Sparse Dimensional tables
Do not separate the parent and child line item data
Managing time-stamps across multiple time-zones
Recording events in multiple currencies
Handle different units of measure in the same fact table
Handling of Null foreign Keys in fact tables
Dimension Attributes as NULL
Don't rely too much on Meta Data Tools to enforce Business Intelligence
Don't wait for universal models for Data Marting
Add extra buffer for ETL phase
Homework before interviews is must (Business Requirements Phase in Data Warehouse)
Excel is the competition, which should be challenged
Avoid Pure MOLAP
Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Consolidate Data-Marts
Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Licensing & Maintenance Contracts
Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Governance & Standards
Field Tips Series- Streamlining & reducing cost of Business Intelligence- Evaluate Open Source
Master Data Management- Making a Right Start
How to integrate stand-alone BI environments- Gradual Approach
Business owned applications are a reality- Manage it
New Data Standards- What about existing data and applications?
Handle Each Time-stamp in the Fact Table as a separate dimension
Keep Aggregates and Details data in different Fact tables
Some considerations for Infrastructure in Data Warehouse
For Core BI platform go for a single, established and robust player
Don't be guided only by the business requirements for your Business Intelligence
Using Synonyms and Views
Additional Channels
Principles & Rules
Free Templates
Glossary
Key Performance Indicators

Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales Campaign Infrastructure
Sales Leads Management System
Sales Cost and Profitability Overview
Sales Channel Data Management
Sales Leads Allocation and Distribution
Read more...
  Customer Relationship Management
Customer Satisfaction & Retention- Data Management
Customer Service and Support - Strategic Role
Drivers for Customer Satisfaction & Retention
Customer Value and Profitability Tips and Actions
Supply Chain for Customer Service and Support
Read more...
  Human Resources & Leadership
Fitting leadership dimension in employee performance
Competencies Definitions
Deliver Results
Feedback does not mean only negative feedback
Business and Financial Acumen
Read more...
 
 
Business Performance & Planning
Strategic Business Plan
Strategic Planning leadership commitment
Stakeholder test for Scorecard
Strategic Planning Business Themes
Internal Info Assessment Report
Read more...
  Business Intelligence & Data Quality
BI Competency Centre- A preface
Universal models for Data Marting
Master-Data-Management CDI Objectives
Scorecard not only business metrics
Don't rely only on business requirements for BI
Read more...
  IT Vendors & Tools Management
OLAP Dimensional Model Change Management
Vendor Company structure Evaluation
OLAP Sever Database Tuning
Business Intelligence Vendor Evaluation
Scalability Technical Evaluation
Read more...