ODE is available as a download from GitHub, which has the instructions for implementing the Configuration Database. Configuration is a heart and brain of ODE Data Vault.
Other organs include stage and vault databases. From ODE version 5 these databases should have a certain structure. Certain database schemas and a special table for the load auditing should exist before users can start modelling the Data Vault.
Download an Admin Visual Studio solution from GitHub. This is a Visual Studio 2015 solution. Right-click on ODE_Stage project in the Visual Studio Solution Explorer. Click “Publish…”. Connect to the server where you have installed the Config database. Provide a meaningful name to your staging database. Click “Publish” when you have finished with the settings. Visual Studio generates database creation script that creates a database with the proper settings, database collation that matches config database collation, adds schema “stage” and creates a service table required for the proper Data Vault load execution.
Do the same with the ODE_Vault project. Publish it on the same server where you have created a stage database. One Config could manage multiple Data Vaults. Each of the next Stage and Vault databases should be created in the same manner. It is recommended to have one stage database per Data Vault. Keep the naming similar for the pair of database. For example, ODE_Raw_Vault and ODE_Raw_Stage, Sales_Vault and Sales_Stage, etc.
Admin Visual Studio solution has a few useful projects which could help with ODE Data Vault experience. Project “ODE_to_MSSQL_Scripts” contains “helper” stored procedures for configuring hubs, links and satellites. Project “ODE_Release_Manager” is an SSIS project that could help with the configuration releases to another server.
Once Config is installed and first databases are created, next step is starting configuration.