I have never worked with SQLServer varbinary, but I think that one of these subroutines will work for you. If you need the binary data in the first output to be transformed into the hex pairs in the second output, then use first_to_second. If you need the reverse, then use second_to_first. 
#!/usr/bin/perl -w
use strict;

my $x = 
'0x0105000000000005150000009E15AE084A7CBC7A881C6A37C63F0000';

open    GG, ">c:/PerlMonks_346728.out" or die;
binmode GG or die;
print   GG second_to_first($x);
close   GG or die;

sub first_to_second {
  return join('', '0x', unpack 'H*', $_[0]);
}
sub second_to_first {
  local $_ = shift;
  s{^0x}{}i or die;
  return pack 'H*', $_;
}

[download]

In reply to Re: SQLServer varbinary headache by Util
in thread SQLServer varbinary headache by bfdi533

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.