Convert(int,sys.fn_sqlvarbasetostr(hashbytes('md5','1455985476'))) | Easy • Release |

For the specific input '1455985476' , the MD5 hash is 792106533f84b730c64951a1ea702c78 . Converting the relevant portion of this hex value to a signed 32-bit integer results in: Common Use Cases

: Distributing data rows into different "buckets" or shards by hashing a unique ID. For the specific input '1455985476' , the MD5

: This attempts to cast that hex string into a 4-byte integer. Because the hash is much larger than an integer, SQL Server typically truncates the value, often resulting in an arithmetic overflow or returning a signed integer based on the last 4 bytes of the hash. The Result Because the hash is much larger than an

: This internal (undocumented) function converts the binary hash into its string representation (e.g., '0x792106533f84b730c64951a1ea702c78' ). A more standard approach in T-SQL is CONVERT(INT,

: Using sys.fn_sqlvarbasetostr is generally discouraged in production code because it is an undocumented internal function. A more standard approach in T-SQL is CONVERT(INT, HashBytes('MD5', '...'), 2) or directly casting the binary to an integer.