This Quick Reference Guide is a basic introduction to the objects in a Data Vault and how to design the required model in the Data vault design category to allow the wizards and model conversions to produce a Raw Vault.
Some things you must be aware of when designing your Data Vault
- All entity names need to be unique with the entity type prefixes and suffixes removed (Case insensitive).
- On the Satellite naming panel, you should not specify prefixes or suffixes that will match the entity type definition prefixes and suffixes.
- All attributes need to be assigned an attribute type and be given a source mapping.
- When generating the load and stage model, do not have differences in the category entity type definitions between the categories "Data vault" and "Load and staging".
- Every Hub, Link, Reference and Code entity will have its own stage entity, as well as for each additional source system.
Known Issues
The Satellites off any Reference and Code entities defined with a composite primary key will have metadata issues in WhereScape RED.
Workaround: Create a duplicate connection with the setting 'Enable automatic creation of indexes' turned off, and a target location created and assigned to the Satellites related to a Reference or Code entity.
Supported in 3D