Read the DBD::Sybase docs carefully. Sybase can return multiple result sets from a query, and most of the system stored procedures do in fact do that. You should structure your result retrieval something like this:

do
{
    while(my $row = $sth->fetchrow_array)
    {
        # do something with the row
    }
} while($sth->{syb_more_results});

[download]
Note that you need to check for syb_more_results after your first call to fetch*.

Update
I forgot to add: some of what dbcc prints isn't even a result set, it's a server message (the output of print). You'll need to install an error handler, as outlined in the docs under "Sybase-specific attributes". There's an example there of how to print showplan output that you can use as a model.

In reply to Re: DBD:Sybase (how to get output from sp_* procs) by VSarkiss
in thread DBD:Sybase (how to get output from sp_* procs) by Bone_Scavenger

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.