EDW Reference Architecture: Metadata
EDW Reference Architecture: Metadata As a final note on the series EDW Reference Architecture, introduced in Why Bother? and continued in discussions on the Acquisition, Integration, Warehousing and...
View ArticleIn Defense of Surrogate Keys
Employing surrogate keys is an essential strategy to protect the integrity of data assets in the EDW. For those looking to defend such a position against those who would prefer human-readable business...
View ArticleReference Domains Part I: Overview of Classifications
Reference Domains, often referred to as Classifications, are essentially the sets of reference codes and descriptions that are used to categorize or classify entities throughout the EDW data model....
View ArticleReference Domains Part II: Modelling Classifications
This is the second article in the series on working with reference domains, also commonly referred to as classifications. In Part I, we looked at the nature of classifications. Here we will discuss...
View ArticleReference Domains Part III: Collecting Classifications
This is part three in the series about reference domains (a.k.a. classifications). In the first part we looked at the nature of classifications. In part two, we discussed a recommended approach to...
View ArticleReference Domains Part IV: Metadata & Governance
This is the fourth and final part in the series on working with reference domains, also called classifications. The first part provided an overview of their nature, the second recommended an approach...
View ArticleNine ETL Design Principles
The principles of ETL design define the guidelines by which data migration will be constructed. Below are 9 principles to guide architectural decisions. 1. Performance In almost all cases, the prime...
View ArticleData Design Principles
Obey the principles without being bound by them. - Bruce Lee Taking a practical approach to developing a well-formed enterprise data warehouse – and by that, I mean one that is accurate, efficient and...
View ArticleMaking the Case for EDW
An EDW enables strategic capabilities for organizations; resolving issues that plague complex technology environments, while creating a solid foundation on which to build new opportunities. Here are 7...
View ArticleData Design is Not Optional
The data model is designed to enforce certain rules on the information – such as ensuring that customer identifiers are never duplicated, that no account exists without a customer to own it, and that...
View Article