Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Can someone explain to me why don’t T-SQL’s
SELECT substring(master.dbo.fn_varbintohexstr(hashbytes('MD5', 'HelloWorld')), 3, 32)
and .NET’s
Convert.ToBase64String(New System.Security.Cryptography.MD5CryptoServiceProvider().ComputeHash(System.Text.Encoding.UTF8.GetBytes("HelloWorld")))
return the same result?
Tsql returns 68e109f0f40ca72a15e05cc22786f8e6 and .net returns aOEJ8PQMpyoV4FzCJ4b45g==
The .net one is base64, the T-SQL one is hex. They are different encodings.
The length of the output tells you that too because MD5 delivers 16 bytes (as per the T-SQL solution)