What Is a Business Key in Data Vault?
A business key is the identifier your employees and customers actually use: the customer number, the invoice number, the contract ID. It is stable, it is shared across systems, and it is what every hub in a Data Vault is built on.
The data warehouse automation solution trusted by data teams across industries
Does this sound familiar?
- The model was designed from the database schema, and the business does not recognize a single key in it.
- After the ERP migration, every customer has a new ID, and the history no longer joins.
- Two systems hold the same customers, and the warehouse cannot tell which records belong together.
A hub is only as good as the key it is built on. In Data Vault, the key to success is the business key.
What a business key is
A business key is the identifier the business itself uses: the customer number on a letter, the invoice number a customer quotes on the phone, the contract ID in an email. Employees and customers know these keys, which is why they are stable. A system can renumber its internal rows; it cannot easily change a number printed on ten thousand invoices.
In classical data modeling terms, the business key is the natural key, one of the entity’s candidate keys, as opposed to the surrogate key a database generates for its own purposes. If you have ever chosen a primary key for a conceptual model, you have already done this work.
How to find them: the paper invoice trick
Many data engineers and modelers hesitate to ask business users about keys. The question sounds technical, and the answers drift into table names. A simple exercise avoids that:
- Ask the business users to print a few real documents: an order, an invoice, a delivery note.
- Ask them: “If a customer calls you about this document, what will they tell you so you can find it?”
- Highlight what they point at.
Those highlighted identifiers are your business keys. The same sheet of paper shows you the concepts around them (customer, order, product) and how they relate to each other, which is the start of the model.
Why Data Vault builds on business keys
- Passive integration. Business keys are shared between source systems. When the CRM and
the ERP both load customer
C-10442into the same hub, their data is connected without any manual integration logic: the shared key and our automation do the work. - Source system migrations. When a source system is replaced, its technical keys change. Its business keys do not, so the history before and after the migration still lines up.
- Data warehouse generations. The same holds for the warehouse itself. When a new data integration or DWH solution has to take over data from the old one, the business keys connect the two, because they are stable between DWH versions as well.
Where the same key means different things in different systems, such as order 1018 in the
Swiss and German ERPs, the Business Key Prefix keeps them apart. Where a
key consists of several parts, such as company code plus customer number, the business key is
simply composite.
The catch
Most source systems store the business key in the entity it defines: the customer number sits in the customer table. The relationships, however, use technical keys. An order row carries the customer’s system-internal ID, not the customer number. How to get from there to a model built on business keys is the subject of the next article in this series, technical versus business keys.
What changes with Datavault Builder
In Datavault Builder, you define the concept once. Then you map every source to it by defining which of its columns form the business key, and Datavault Builder does everything necessary for the integration to happen: the hub, the key handling, and the loading code are generated. The effort goes into the conversation with the business, not into writing load logic.
See It Running on One of Your Sources
Book a free demo and bring the connector that costs you the most, in money or in time.
Three Steps to Your Business Keys
-
Print the documents
Ask the business users to bring real orders, invoices and delivery notes to the first session.
-
Ask one question
If a customer calls about this document, what do they tell you to identify it?
-
Highlight the answer
Every identifier they point at is a business key. The documents also show the concepts and how they relate.
How Datavault Builder Takes the Friction Out of Ingestion
-
Ingestion is built in
Batch, delta and CDC loads from databases, files, REST APIs, NoSQL and Python sources, with streams such as Kafka arriving as micro-batches. Same platform that generates the warehouse, no second invoice.
-
Your schema, not the vendor's
Source tables are mapped to a Data Vault 2.0 model you designed. A new column or a renamed table changes a mapping, not a chain of post-load scripts.
-
Only deltas move
Hubs, links and satellites load what changed. Full reloads stay in staging instead of being reprocessed downstream every night.
-
History is kept by design
Every change is retained as it arrives, so as-was reporting works even where the source overwrites its own rows.
-
Code you never hand-write
Loading, historization and lineage are generated from the model in real time and run natively on Snowflake, Databricks, BigQuery, SQL Server, Fabric, Oracle or PostgreSQL.
-
One platform, up to nine tools fewer
Modeling, ETL, CI/CD, documentation and lineage in one place. That is what makes 14.7 minutes from requirement to production possible.
Recognized by BARC in The Data Fabric Survey 26
Meet Our Expert
Twenty minutes with our Sales Director, and an honest answer on whether this fits your stack.
Matt Collett
Sales Director
Great, pick a time that works for you:
Other Problems This Series Covers
-
Technical Keys vs. Business Keys in Data Vault
Source systems keep the business key in the master record, but every relationship runs on technical keys. Four ways to deal with that, what each one costs, and the pattern we use: a PSA hub for the technical keys, mapped to the business key hub.
-
What Is a Satellite in Data Vault?
A satellite holds everything that describes a hub: names, statuses, amounts, and every change to them, appended and never updated. It is a slowly changing dimension type 2 without the UPDATE, with a full audit trail built in.
-
What Is a Link in Data Vault?
A link records that business keys belong together: this order belongs to this customer. Datavault Builder covers the classic Data Vault link, and adds a transaction link anchored on a grain hub, which fixes the grain of a transaction and lets transactions relate to each other.
-
What Is a Hub in Data Vault?
A hub represents one core business concept, such as customer, product or account, as the list of its keys: every one the warehouse has ever seen, each exactly once. It stores identity, not state, and that restraint makes it the point where source system silos collapse.
Questions and Answers
- Dan Linstedt. He developed the method in the 1990s and published it around 2000. Data Vault 2.0, which adds hash keys, a methodology and an architecture around the model, followed in 2013.
- The standard reference is Building a Scalable Data Warehouse with Data Vault 2.0 by Dan Linstedt and Michael Olschimke (Morgan Kaufmann, 2015).
- No. Bill Inmon sees Data Vault as an evolution of his third normal form view of the enterprise data warehouse, not as a competing approach.
- No. A dimensional output is often part of a Data Vault implementation: the vault keeps the integrated history, and star schemas are built on top of it for reporting. The same vault can also deliver flat tables or a Unified Star Schema.
- With automation, a third normal form view on top of a Data Vault can be generated completely deterministically. The vault holds the data once, and the 3NF layer is derived from the model. How that works.
- Trying it without automation. Data Vault is built on a small set of strict, repeating patterns, which is exactly what makes it tedious and error prone to write by hand and straightforward to generate. That is why you should use Datavault Builder.
- Yes. Splitting keys, relationships and history into hubs, links and satellites means more tables than a normalized or dimensional model. That is why the physical layer should be abstracted by a model-driven approach like Datavault Builder, where you work on the business model and the tables are generated.
- Book a demo and see a Data Vault built on your own sources, or order a training environment and try it yourself.
- Here. Datavault Builder is a Data Vault automation solution: see pricing or book a demo.
- Datavault Builder is licensed annually, as a subscription to use the software. Perpetual licenses are available on request. The editions and what they include are on the pricing page.