From: sheldonlg@thevillages.net   
      
   On 6/20/2014 10:16 AM, Erland Sommarskog wrote:   
   > Shelly (sheldonlg@thevillages.net) writes:   
   >> Anyway, I have the solution.  It is to enclose the HASHBYTES stuff with   
   >> the following:   
   >>   
   >> SUBSTRING(master.dbo.fn_varbintohexstr(  hashbytes calculation ), 3, 32).   
   >>   
   >> The result is a 32 character hex string put into the tracking table.   
   >>   
   >   
   > If you are on SQL 2008, use   
   >   
   >    convert(varchar(32), hashbytes, 2)   
   >   
   > instead, as this is a documented and supported way to get a hex string.   
      
   It didn't work.  I got something like:   
      
   Msg 245, Level 16, State 1, Line 1   
   Conversion failed when converting the varchar value   
   '04B2D57D287ADE502C621C3534C574' to data type int.   
      
   --   
   Shelly   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)