primary key options for data vault 2.0 this entry is a candid look (technical, unbiased view) of the three alternative primary key options in a data vault 2.0 model. there are pros and cons to each selection. i hope you enjoy this factual entry. (more…)
a short walk through what the data vault is really about. i hope you enjoy this lesson. i’ve got plenty of customers achieving / receiving real business value – monetary value, from their data vault 2.0 solutions, and yes, they are able to see the data as an asset as a result of this process.
a short entry explaining the thought process behind the switch in dv2 away from sequences over to hash keys. also describes some of the issues if natural or business keys are selected instead of hashes as primary keys in the data vault model.
the second in a series describing the nature of attaching value to your data, and why business keys are so important, especially with nosql, big data, and data lakes.
a look at address and people based business keys, how they are sticky, and the best possible solution to deal with them
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.
a quite lengthy entry on the nature of business keys, and the discussion of how the data vault model plays a role in architecture and design.
a short trip down memory lane in exploring md5 hashes as primary keys in the data vault. i also discuss the business data vault, and the operational data vault in passing.
short discussion on business keys, and what to do when you can’t find the right one for the hub’s purposes.