a look at address and people based business keys, how they are sticky, and the best possible solution to deal with them
in this entry i will explore the use of implementation of data vault on teradata. however, this entry is applicable to everyone in the data vault community, as it covers definitions and descriptions of primary keys, indexing, surrogate keys, natural keys, and performance and tuning.
the more i go, the less i like the idea of composite business keys being candidates for hubs. here, i present a source system scenario, and explain how it plays out in creating a data vault as far as creating hubs go.
lengthy questions about the canonical structure, conceptual vs physical data vault modeling, raw data vault vs business applications. an interesting read, please add your own comments to the end of this posting.
discussion and answers about www.tdan.com articles, some clarifications of statements i made in 2001/2002. i think you might find this interesting.