Choose a tab to view either setting descriptions or examples.
Group | Section | Type | Setting | Description |
---|---|---|---|---|
Core | Defaults | Hash Null Value Replacement | The Null value replacement to be used when hashing | |
Core | Defaults | SSIS Hash Null Value Replacement | The Null value replacement to be used when hashing using the Varigence BimlFlex SSIS Custom component. Provides backwards compatibility when set to an empty string. For new implementations and SQL hash compatibility, set to the same value as used for HashNullValue | |
Core | Defaults | Integration Key To Upper | Should strings in the Integration Key be uppercased. This is recommended and allows the standard SQL Server case insensitive collation to ingest business keys from multiple sources using different casings to be added to Hubs and treated as the same key without issues | |
Core | Defaults | String Concatenator | The string value used in concatenating Integration Keys and Hash values. Defaults to "~". For a source column with an "SsisDataflowExpression" using the "FlexToBk(@@rs,ProductId,OtherAttribute)" expression the resulting string Integration Key would be similar to "AWLT~680~XYZ", concatenating the record source of the connection, the ProductId column value and the OtherAttribute column value | |
Data Vault | Accelerator | Use Hash Keys | Should the Data Vault use Hash Keys or Natural Keys | |
Data Vault | Accelerator | Accelerate Link Satellite Keys | Should the accelerator add the Integration Key to the Link Satellites for effectiveness | |
Data Vault | Accelerator | Accelerate Hub Keys | Should the Accelerator add source key columns to the Hub in addition to the Integration Key | |
Data Vault | Accelerator | Accelerate Link Keys | Should the Accelerator add source key columns to the Link in addition to the Integration Key | |
Model | Settings | Infer Integration Key From | Where to infer the Integration Key from. Case sensitive options are "None", "PrimaryKey", "UniqueKey", "FirstColumn", "IdentityColumn" and "ColumnName::[NameOfColumn]". When specifying "ColumnName", a name needs to be added in the Import Metadata screen or specify "ColumnName::UID" to auto populate the column name field with "UID" |
|
Model | Settings | Pad Integration Key | Number of Characters to pad the Integration Key to | |
Model | Settings | Append Integration Key | The string to append to Integration Keys | |
Model | Settings | Add Record Source To Integration Key | Import Metadata will add "@@rs" to Integration Keys if true | |
Model | Settings | Change References To Integration Key | Should Import Metadata add derived Integration Keys from source references or use source columns for references | |
Naming | Naming | Suffix Or Prefix Column | The "SuffixOrPrefixColumn" key defines the behavior when defining column names. Use Suffix or Prefix to define if the column identifiers are added after or before the column names in the solution. "S" for Suffix will generate "Entity_BK" "P" for Prefix Will generate "BK_Entity" |
Group | Section | Type | Setting | Default Value |
---|---|---|---|---|
Core | Defaults | Hash Null Value Replacement | NVL | |
Core | Defaults | SSIS Hash Null Value Replacement | ||
Core | Defaults | Integration Key To Upper | true |
|
Core | Defaults | String Concatenator | ~ | |
Data Vault | Accelerator | Use Hash Keys | true |
|
Data Vault | Accelerator | Accelerate Link Satellite Keys | true |
|
Data Vault | Accelerator | Accelerate Hub Keys | false |
|
Data Vault | Accelerator | Accelerate Link Keys | false |
|
Model | Settings | Infer Integration Key From | PrimaryKey | |
Model | Settings | Pad Integration Key | 100 | |
Model | Settings | Append Integration Key | BK | |
Model | Settings | Add Record Source To Integration Key | true |
|
Model | Settings | Change References To Integration Key | true |
|
Naming | Naming | Suffix Or Prefix Column | S |