Choose a tab to view either setting descriptions or examples.

Group	Section	Setting	Description
Data Vault	Accelerator	Accelerate Link Satellite	Should the accelerator create Link Satellites for effectiveness and attributes from source metadata
Data Vault	Accelerator	Accelerate Link Satellite Keys	Should the accelerator add the Integration Key to the Link Satellites for effectiveness
Data Vault	Accelerator	Append Link Satellite Record Source	Should the Accelerator append the RecordSource to the Link Satellite name
Data Vault	Accelerator	Accelerate Link Keys	Should the Accelerator add source key columns to the Link in addition to the Integration Key
Data Vault	Accelerator	Stage Reduce Link Keys	Enable this to reduce additional Link hash keys in the staging table
Data Vault	Accelerator	Accelerate Two Way Links	Should the Accelerator split all Links into Two Way Links or combine all Non Nullable references into a single Link or Unit of Work
Data Vault	Process	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	Append Link	The string to append to Link names
Data Vault Naming	Naming	Append Link Satellite	The string to append to Link Satellite names
Data Vault Naming	Naming	Append Hierarchy Link	The string to append to Hierarchical Link names
Data Vault Naming	Naming	Append Same As Link	The string to append to Same As Link names
Model	Settings	Key Ends With	The strings that BimlFlex interprets as key identifiers. For a source table with a column "ProductCategoryId" that links to a ProductCategory table, BimlFlex will create a Model Reference called "ProductCategory" as name

Group	Section	Setting	Default Value
Data Vault	Accelerator	Accelerate Link Satellite	`false`
Data Vault	Accelerator	Accelerate Link Satellite Keys	`true`
Data Vault	Accelerator	Append Link Satellite Record Source	`true`
Data Vault	Accelerator	Accelerate Link Keys	`false`
Data Vault	Accelerator	Stage Reduce Link Keys	`false`
Data Vault	Accelerator	Accelerate Two Way Links	`false`
Data Vault	Process	Infer Link Hub	`false`
Data Vault Naming	Naming	Append Link	LNK
Data Vault Naming	Naming	Append Link Satellite	LSAT
Data Vault Naming	Naming	Append Hierarchy Link	HAL
Data Vault Naming	Naming	Append Same As Link	SAL
Model	Settings	Key Ends With	Id,Code,No,Key