5.1 Creating a new data vault

In the menu bar, select Data Vaults.

Add a new data vault.

Click the

button to set the data vault specific parameters. The parameter group, Technology dependent parameters, only shows up here since these parameters depend on the database type of your data vault.

For example, the ETL/ELT generation type can be SQL (PL/SQL,PL/pgSQL,T-SQL, etc.) or an ETL tool such as ODI, Talend or Informatica. Furthermore, default formats can be changed, such as dates, times, numbers etc.

In general, there will be only one data vault per project and database type. However, it is possible to create more.
Go to the Releases tab and add a new release. You will have to choose a name and number for your release, as well as select which version of the sources will be used. Remember that sources for which the build flag is off, will not be included.

The Releases tab shows you all the releases made for a data vault. Again, the lock icon at the end shows whether this build has been locked or not.

The production date field should be filled in when you have deployed your data vault. If one of your sources changes, you must first create a new release for that source, complete it and then create a new data vault release. This new release will only build further on previous releases that have been locked and have a production date. If you made a data vault release and it included some extra objects by mistake, but you haven’t set a production date for this release, these new objects will not be included in the next release of your data vault, if removed from the new source release. Objects in a data vault release with a production date cannot be deleted. Setting the production date will also lock the schema, object and attribute name parameters, since these should not be changed after deploying your data vault and could cause problems otherwise.