The sample models used in TEAM and VDW
This page contains additional information on the demonstration models / environment for the Virtual Data Warehouse. To be able to do this the software and repository must be installed.
The sample models, metadata and patterns contain various Data Vault use-cases, and can be a great tool to understand how Data Vault patterns work.
All models have been created in SQL DBM, a database diagramming tool for simple data models. Unfortunately the feature to use links to point to specific model versions has been disabled recently, so screenshots of the models are provided instead.
Making (meta)data available for VDW using TEAM
VDW itself does not need a database connection, as it uses Json files containing the metadata output conforming to the schema for Data Warehouse Automation. For managing the metadata itself, and saving it in this output format, the TEAM application can be used (or other metadata management tools or text editors).
From TEAM it is possible to generate the original sample databases and metadata, the setup that was used to generate the Json metadata files that VDW consumes and generates code with.
Creating the sample environment from TEAM will deploy the areas outlined below, depending on which database connection is linked to the samples in TEAM.
For this, you can create one or more databases depending on how you would like to set up your system. In the standard example a database is created to install each area into. As a fun thought, you can also generate these structures from VDW by using the DDL patterns – although I haven’t created patterns for every table structure at the time of writing.
For example, create a new ‘EDW_000_Source_Database’ database (or something of your own choosing) to connect the source sample set to in TEAM so the application can create the sample tables and data in this designated database.
Source
This area acts as proxy ‘source system’ / OLTP system and will contain some sample data.This is the only area where data is created, as everything will be loaded into the other tables from here.
Staging Area
This is the Staging Area of the Enterprise Data Warehouse.
Persistent Staging Area
This is the historical archive / history area.
Integration Layer
This database will contain the Raw and Business Data Vault models.
Presentation Layer
This is the database that prepares the information for further consumption, in our case it houses the Raw Mart (as-is Dimensional Model).