in reply to Trapping Stroed Proc errors with MSSQL
Second - try running this with DBI->trace(3) to see what the server sends back, and how your DBD driver interprets this.
Michael