Re-write:
- Normalization and Further Normalization Part 1: Databases Representing What
- Normalization and Further Normalization Part 2: If You Need Them, You're Doing It Wrong
Making friends is truly the beginning of making lasting memories. To make friends with science is truly to start with making good friends that make lasting memories about science. I'm starting a new revolution in the way science will be made socially for the community and ask the community to step in and help make science fun, engaging, real, social and most importantly lasting friendships.
The Principle of Orthogonal Database Design Part I
The Principle of Orthogonal Database Design Part I
From my experience, that traditional model has changed as data warehouses are being driven to near real time business intelligence and used as a common repository for disparate systems. The separation between front line systems and data warehouses was due to software and hardware demands could not handle a mixed work load, minimizing costs, plus application products requiring different data stores. The world has moved on. There are DBMS's that can handle mixed work loads with enormous scalability. Application products are becoming broader in business features. Pricing models have changed.So the whole idea of a distinction between operational databases and data warehouses significant enough to require distinct database technologies, let alone deviations from the relational model, has not exactly held water, has it? Which was pretty predictable.