Please reverse the decision to depreciate HASHBYTES (MD5 & SHA1). They are a core requirement for Data Vault 2.0. Given its growing popularity as a data warehouse design methodology. The demand for that functionality is set to increase.
I noticed that we’ve depreciated support for many of the HASHBYTES algorithms. (leaving only SHA2_256 & SHA2_512) https://msdn.microsoft.com/en-AU/library/ms174415.aspx?f=255&MSPPError=-2147217396
No doubt the logic behind the decision is the earlier algorithms are cracked & inappropriate for crypto.
I’d suggest we rethink that decision.
There is a growing interest in Data Vault 2.0 as a Data Warehouse design methodology.
This approach depends heavily on hashing keys, most often MD5 & SHA1 are the recommended approaches.
These hash keys are used as “almost” unique identifiers. They are applied to natural keys whose length is often too small to use SHA2 algorithms.
They are recommended by DV2.0 because most platforms support them & they are computationally lighter weight. Thus similar to a GUID, Hashed keys can be generated by many heterogeneous systems in parallel, & loaded into a single Staging database with “minimal” probability of collision.
Depreciating these algorithms will create uncertainty for the DBA’s who are considering using SQL Server as the platform for their Data Vault 2.0 data warehouse.
PS: While we could debate the wisdom of such an approach given the risk of Hash Key collisions. But that is for the DV2.0 guys to argue. We just want to remain relevant.