Clear all

Creating New Hub in the Business Vault

Posts: 0
Topic starter
Joined: 52 years ago



I have a situation when it makes sense for me to create a new derived HUB table to model a customer need met (ie risk neet met, savings need met) I am still new to Data Vault and would like to understand if there are arguments for or against creating a new HUB with a derived business key (essentially I could give each need a code and standardize on this as the business key going forward?)

Modelling these as attributes in a SAT has meant I have to model new needs as columns and change table structures instead of modelling the relationship in a LINK table as rows which gives me much more flexibility and enables me to create new business need relationships without changing table structures or creating a single new satellite table as we add needs in an agile development cycle.

Is there any guidance when creating new Hub tables that do not naturally occur in the source or raw vault?

Topic Tags
15 Replies