Data warehouse architecture that’s too narrowly focused

In my DM Review columns, “The Accidental Architecture” and “Recovering from the Accidental Architecture,”
I discussed whether people understood the “why” of best practices, such
as dimensional modeling and hub-and-spoke architecture. In “Don’t Stop at How, Learn Why,”
I discussed the most common problems when people are too hub myopic,
cloning their source systems or assuming the hub will support all
reporting and analytic needs.

There are also
dangers with being too spoke-centric (with data marts or cubes) and
failing to establish the hub, or data warehouse (DW), as the enterprise
data backbone.

More Read

Forecasting Lessons from Heathrow’s Snowpocalypse

Data Virtualization: 6 Best Practices to Help the Business ‘get it’

4 Spectacular Ways Conversational AI Improves Customer Experiences

Defeat Common Hurdles to Make Big Data More Effective for Marketing

“Predictive analytics allows your organization to learn from its collective experience and puts this…”

>>> Read the rest of my article "Too Narrowly Focused" on the DM Review website.

Link to original post