Introduction to This Course

Welcome !

Just a few house-keeping notes for you before you get started:

  1. This course follows every standard that we define in Data Vault 2.0
  2. There is a difference between a standard and a best practice.
  3. Standards are enforceable and when broken, will break one or more of the following: scalability, ease-of-use, optimization, maintainability, and more.
  4. Best Practices are not enforceable, these are strongly encouraged practices – methods and designs for you to apply.

Not using End-Dating is a best practice, NOT a standard.   We highly discourage the use of end-dating, however people see a need and have implemented end-dating in the Data Vault since the beginning of their journey.  We therefore demonstrate the use of end-dating in business driven satellites – prefixed with “bv_” in the data model.  For this reason we are free to execute business rule calculations that set these end-dates, and update the fields.   End-dates are not in use in Hubs, Links, raw Satellites, and we have at least one (if not two) Effectivity Satellite cases that are designed as 100% insert driven.   For this reason, you can see both patterns and learn both approaches.

We recommend 100% insert driven best practice, especially for scalability in to the trillions of records.

Standard: All Hubs carry business key attributes.

Best Practice: Leverage Hash Keys as “surrogate keys” or replacement keys for your primary keys in your Hub Structures.   Going forward – this practice may vary depending on platform and physical capabilities to execute without hashing in place.    For now, most database platforms do well with the hashing practices.

Lastly: please don’t forget to fill in the survey at the end of the course – it is the last lesson.  Why?  Your feedback is important to us, and it’s the only way we can know how to improve the course going forward.

We hope you enjoy this course,  Thank You!