The Varigence company brand logo
Products
BimlFlexBimlStudioBimlExpress
Pricing
Solutions
IndustriesUse Cases
Resources
DocumentationKnowledge BaseBlog
About
CompanyContact Us
Products
BimlFlexBimlStudioBimlExpress
Pricing
Solutions
IndustriesUse Cases
Resources
DocumentationKnowledge BaseBlog
About
CompanyContact Us
Schedule Demo
Account
Schedule Demo
Account
  • Select:
  • Description
  • Default Value

Choose a tab to view either setting descriptions or examples.

Group Section Type Setting Description
Data Vault Accelerator Boolean Datatype Use Hash Keys Should the Data Vault use Hash Keys or Natural Keys
Data Vault Accelerator Boolean Datatype Accelerate Hub Keys Should the Accelerator add source key columns to the Hub in addition to the Integration Key
Data Vault Process Boolean Datatype Infer Link Hub Should the Data Vault load from a staging table also load all secondary hubs that are part of any Link loads. For scenarios where the referenced table loads all keys as part of the same process it is normally possible to defer that load to the separate table.

Sample Scenario:

A source to staging to Data Vault load is done on the "Product" and "ProductCategory" tables from AdventureWorksLT.

The Product table populates the HUB_Product table. The ProductCategory table populates the HUB_ProductCategory table.

The Product table contains a FK constraint to the Product Category and the ProductCategoryId column in the Product table refers to the category a product is in.

The normal Link load would use the Product BK and the Product Category BK defined in the Product source table metadata to load the Link. It would not load any data in to the HUB_ProductCategory as that is being loaded from the ProductCategory source table.

As this is a database source it is probably safe to assume the referential integrity in the source means all ProductCategory BK data in the Product table is also in the ProductCategory table. As such it is unnecessary to load that data twice.

For other sources it might be necessary to load the HUB table from both sources, either due to late arriving data, missing data or as a prudent safety measure to ensure it is possible to inner join Link and Hubs without losing rows.

Setting the "DvInferLinkHub" to true will allow the Product to populate the ProductCategory Hub as part of that source table load
Data Vault Naming Naming Text Datatype Append Hub The string to append to Hub names
Naming Naming Text Datatype Suffix Or Prefix Object The "SuffixOrPrefixObject" key defines the behavior when naming objects.

Use Suffix or Prefix to define if the object identifiers are added before or after the object names in the solution.

"S" for Suffix Will generate "Entity_HUB"

"P" for Prefix Will generate "HUB_Entity"
Group Section Type Setting Default Value
Data Vault Accelerator Boolean Datatype Use Hash Keys true
Data Vault Accelerator Boolean Datatype Accelerate Hub Keys false
Data Vault Process Boolean Datatype Infer Link Hub false
Data Vault Naming Naming Text Datatype Append Hub HUB
Naming Naming Text Datatype Suffix Or Prefix Object P

© Varigence