Return to Question

(I will still be using the spooky hash on this binary result. The workload uses hash joins and the hashed value is used for one of the hash builds. I don't want a long binary value in the hash build because it requires too much memory.)

• If it matters, a significant majority of the time (90%+) the columns won't be NULL.
• I have to use the CLR.
• I have to hash this many rows. I cannot persist the hashes.
• I have to do this in SQL Server.
• I believe that I cannot use batch mode for the conversion due to the presence of the CLR function.

• If it matters, a significant majority of the time (90%+) the columns won't be NULL.
• I have to use the CLR.
• I have to hash this many rows. I cannot persist the hashes.
• I believe that I cannot use batch mode for the conversion due to the presence of the CLR function.

It does not handle NULLs correctly. If COL1 is NULL for row 1 and COL2 is NULL for row 2 then both rows will be converted to a NULL string. I believe that correct handling of NULLs is the hardest part of converting the entire row correctly.

It does not handle NULLs correctly. If COL1 is NULL for row 1 and COL2 is NULL for row 2 then both rows will be converted to a NULL string. I believe that correct handling of NULLs is the hardest part of converting the entire row correctly. All allowed values for the INT columns are possible.