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

For a Data Warehouse/Data-Mart solution, analyze well, but be decisive

Data Warehouse is one solution which can be implemented in million different ways. People have to maintain a right balance between analysis and time-bound decisions.
 
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,

For a Data Warehouse/Data-Mart solution, analyze well, but be decisive

A Data warehouse has following decision points (ranging from business to outright technical):

  • The width of business information (type of business information needs it will satisfy)
  • The time horizon of business information (last one year v/s last ten years)
  • The depth of business information (the level of granularity)
  • The number of source systems.
  • The level of quality
  • The kinds of schema
  • The level of aggregations (totally granular v/s aggregations to satisfy high frequency queries)
  • The approach towards slowly changing dimensions (which method to apply)
  • Data integration approach (Data federation vs conventional ETL)
There is no limit to the level of discussions one can have around these and many other decision points. However one has to start somewhere. Like most of other management situations, one has to follow the following decision making principles:
  • Get some external view on how other companies are doing. Be part of Industry user groups.
  • Postpone decisions which can have lower impact if they are taken later.
  • Start small and don't go for big-bang incase this is your first foray with Data Warehouse.
  • Fix an arbitrator, whose decision can be considered as final.
  • Design your DW in a way, so that changes at later stage are not over-whelming. A well-designed dimensional modeling can provide future extensibility.

Quick Feedback- Was this information helpful ?
Relevant Links to this page
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 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 Compensation Structure Decision
Sales Leads Allocation and Distribution
Sales Compensation Management
Sales Channel Partner Acquisition
Sales Campaign Business Intelligence
Read more...
  Customer Relationship Management
Customer Segmentation Actions
Customer Service and Support Overview
Customer Knowledge and Organizational Knowledge
Customer Segmentation approach
Customer Value and Profitability Data Management
Read more...
  Human Resources & Leadership
Fostering Innovation
Feedback does not mean only negative feedback
Develop Self and Others
Act with Decisiveness
Strategic Business Plan
Read more...
 
 
Business Performance & Planning
External Info Assessment Report
Strategic Vision and Mission
Strategic Planning Business Themes
strategy blueprint Rationalize Align and Publish
Scorecard Health Checklist
Read more...
  Business Intelligence & Data Quality
System Quality Assessment Tool
Data Quality Gap Impact Assessment
Data Warehouse ETL Loading
OLAP Server Layer and capabilities
What is Data Warehouse?
Read more...
  IT Vendors & Tools Management
Vendor Commercial Evaluation- Billing structure
Report objects for Enterprise Reporting
Business Intelligence Vendor Evaluation
Single point vendor needs to be cost-effective
Metadata Tool Change Management
Read more...