Greetings.

I am trying to add some debug to a stored procedure.

I put some statements like this throughout the code:

select 'some message here';

but I never see them.
I put them in a test procedure that works fine, so that I have a feeling that
when an insert fails in a down-stream try catch block, it messes up the
display of the information.

Can someone tell me how to best go about outputting debug I can see from a
stored procedure, or if I am even correct about try catch blocks throwing
errors, messing up the debug visibility.

I can post code if necessary. Just a general debug question here.
thanks
Jeff Kish

Jeff Kish (jeff.kish@mro.com) writes:
> I am trying to add some debug to a stored procedure.
>
> I put some statements like this throughout the code:
>
> select 'some message here';
>
> but I never see them.
> I put them in a test procedure that works fine, so that I have a feeling
> that when an insert fails in a down-stream try catch block, it messes up
> the display of the information.
>
> Can someone tell me how to best go about outputting debug I can see from a
> stored procedure, or if I am even correct about try catch blocks throwing
> errors, messing up the debug visibility.

I don't have any experience of the TRY-CATCH block messing up the output.
If the debug SELECT does not appear, my interpretation is that the
SELECT statement is never executed. That is, you never reach that part
of the code.

Seeing the actual code would make it easier to say what is going on.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Tue, 15 May 2007 21:37:39 +0000 (UTC), Erland Sommarskog
<esquel@sommarskog.se> wrote:

>Jeff Kish (jeff.kish@mro.com) writes:
>> I am trying to add some debug to a stored procedure.
>>
>> I put some statements like this throughout the code:
>>
>> select 'some message here';
>>
>> but I never see them.
>> I put them in a test procedure that works fine, so that I have a feeling
>> that when an insert fails in a down-stream try catch block, it messes up
>> the display of the information.
>>
>> Can someone tell me how to best go about outputting debug I can see from a
>> stored procedure, or if I am even correct about try catch blocks throwing
>> errors, messing up the debug visibility.
>
>I don't have any experience of the TRY-CATCH block messing up the output.
>If the debug SELECT does not appear, my interpretation is that the
>SELECT statement is never executed. That is, you never reach that part
>of the code.
>
>Seeing the actual code would make it easier to say what is going on.
thanks.
knowing nothing 'mysterious' is going on means I need to double check again
for ignorance on my part.

Jeff Kish