I'll define approach as a combination of methodology (build-out schedule) and architecture (data flows and structures)....
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Both Bill Inmon and Ralph Kimball have made tremendous contributions to our industry.
I have an entire presentation on this subject, but I'll try to boil it down here. There are fewer differences than people think between the two approaches to data warehouse design. It's mostly a matter of different focuses (Inmon - architecture, Kimball - modeling) and slightly different terminology.
I strongly believe that customization and extension are required for each situation. Neither approach is comprehensive to answer all questions nor remove your need to apply judgment.
You'll have two basic decisions to make and numerous follow-on decisions:
- Enterprise vs. Data Mart-Oriented Architecture
- Enterprise vs. Bottoms-up Oriented Methodology
Example follow-on decisions:
- Build out scope
- Business involvement
- Definition of data marts - units of work or physical expansiveness of use with ETL tool in ETL
- Processes data access options and manner of selection - by use, by enterprise, by category
- Data retention and archival definition of data marts - units of work or physical expansiveness of use of ETL tool in ETL processes
- Granularity of data capture integration strategy – virtual and physical metadata handling modeling technique(s) need, utility and physical nature of data marts
- Operational reporting and monitoring - real-time data warehouse, EAI, BAM performance management
- Persistence, need and physical nature of data staging
- Physical instantiation of operational data stores - single-source, multi-source
- Program development team engineering technology selection process - framework, best-of-breed
- Source work effort distribution - source team, data warehouse team, shared
- Use of operational data stores for source systems - selective, complete
Especially for "large" (or potentially large) data warehouses, I favor EDW architecture and a quasi-bottoms-up methodology. It's like how I conclude the presentation: "The best approach seems to be a hybrid quasi enterprise architecture and hybrid, but rapid, development methodology with some up-front work and use of standards with broadly defined enterprises and federation techniques used to unite large enterprises."
Dig Deeper on Data warehouse software
Related Q&A from William McKnight
There are loads of business intelligence tools out there on the market today. Our business intelligence expert provides some valuable resources for ...continue reading
Find out how Oracle’s acquisition of Sun may affect Oracle data warehouse strategy and what it means for users. Also, see what role packaged BI ...continue reading
Find out when you should use a DBMS with your data warehouse, and learn about the future of data warehousing data management and current state of ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.