Subject | Re: Debugging Stored Procedures |
---|---|
Author | Adam |
Post date | 2007-03-15T00:11:17Z |
Hello Robert,
outputs whatever you pass in to OutputDebugString. We then use
DebugView to watch the running commentary.
We pull out these lines before shipping, and although our UDF library
we distribute does contain this function, it is a blank procedure.
In your particular case, this exception is not coming from your stored
procedure per se. You only have one select, and that is in a for loop
so there is no singleton requirement. You do however have an insert
and an update statement. I bet that this table has an insert or an
update trigger.
Adam
> Is there any way to debug a stored procedure?We have a crude but effective way. We have a UDF function call that
outputs whatever you pass in to OutputDebugString. We then use
DebugView to watch the running commentary.
We pull out these lines before shipping, and although our UDF library
we distribute does contain this function, it is a blank procedure.
In your particular case, this exception is not coming from your stored
procedure per se. You only have one select, and that is in a for loop
so there is no singleton requirement. You do however have an insert
and an update statement. I bet that this table has an insert or an
update trigger.
Adam