Choose a tab to view either setting descriptions or examples.

Group	Section	Setting	Description
Core	Hash	Hash Algorithm	The hashing algorithm to use. ("MD5"/"SHA1"/"SHA2_256"/"SHA2_512")
Core	Hash	Hash Binary	Should the generated hash value be stored as a binary representation rather than a string representation
Core	Hash	Hash Integration Key	Should the Integration Key be hashed. This is done automatically for any project where the destination connection integration stage is Data Vault as it is a requirement for a Data Vault load. For other load process designs the hashing is optional and controlled by this flag as well as the hashing configuration in the configuration sheet
Core	Hash	Use SQL Compatible Hash	Should the SSIS inline hashing component use a hashing approach compatible with the SQL Server "HASHBYTES()" function. This is recommended so that the hashed values can be recreated using standard SQL queries when needed
Core	Hash	Use SQL Compatible Row Hash	Should the SSIS inline hashing component for Full Row Hashing use a hashing approach compatible with the SQL Server "HASHBYTES()" function. The default is false for backward compatibility however we recommend true for new projects to make it forward compatible with cloud deployments
Core	Hash	Cast Boolean to True False for Hash	Should the SQL inline hashing function for MSSQL, SQLDB and Synapse convert BIT (Boolean) values to True/False instead of 1/0
Data Vault	Accelerator	Use Hash Keys	Should the Data Vault use Hash Keys or Natural Keys
Staging	Settings	Add Row Hash Key Index	Enable to add a unique, non-clustered constraint on the RowHashKey and EffectiveFromDate columns in staging tables

Group	Section	Setting	Default Value
Core	Hash	Hash Algorithm	SHA1
Core	Hash	Hash Binary	`false`
Core	Hash	Hash Integration Key	`false`
Core	Hash	Use SQL Compatible Hash	`true`
Core	Hash	Use SQL Compatible Row Hash	`false`
Core	Hash	Cast Boolean to True False for Hash	`false`
Data Vault	Accelerator	Use Hash Keys	`true`
Staging	Settings	Add Row Hash Key Index	`false`