Issue: HASHBYTES ( algm, str) function generated hash code differ from regular/ other MD5 programs by the data type. Data: 'mypassword1' If you pass a variable as below as mentioned in the link in 'Ref' below, DECLARE @HashThis nvarchar(4000); SELECT @HashThis = CONVERT(nvarchar(4000),'mypassword1'); SELECT HASHBYTES('MD5', @HashThis ); GO ---- This will generate a Hashed code : 0xBAE02911AA20CACE81224DCA98610B05 If you try the same in different MD5 generator tool like this website : Type 'mypassword1' http://www.miraclesalad.com/webtools/md5.php ---- the generated Hashed code will be, 0d28e4080dc8f64fc9603639bb7aa1b9 Hashcodea are different. Cause: SQL Server differs the algorithm by the data type - here it is not just string , it is nvarchar / varchar - SQL Server adds up spaces or truncate them as to the size of the data. DECLARE @HashThis nvarchar(4000); SELECT @HashThis = CONVERT(nvarchar(4000),'mypassword...
From the tech stacks I climbed and learned