Re: Ignore SQL Server 2000 store proc errors and still get results?
- From: "Mary Chipman [MSFT]" <mchip@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 10 Aug 2005 16:43:27 -0400
Do you have control over the stored procedures? The optimal way to
handle server-side errors in this situation would be to NOT use
raiserror and instead return the expected @@error values in output
parameters instead. That way you can decide in your client-side code
whether or not to ignore the output parameter values without
triggering an exception. Raising errors and handling exceptions is
expensive in both server and client code.
--Mary
On Wed, 10 Aug 2005 14:39:30 -0400, "Mike Jansen"
<mjansen_nntp@xxxxxxxx> wrote:
>We have a SQL Server 2000 stored procedure that raises errors when run.
>Because of what it is doing, this is expected. However, we have result sets
>that are also being returned from the stored procedure.
>
>Using either DataAdapter or SqlDataReader, we'd like to be able to execute
>the stored proc and still get the result sets back. However, exceptions are
>thrown whenever the stored proc raises an error. Is there any way to ignore
>or suppress these errors and still get the result sets?
>
>Thanks,
>Mike
>
.
- Follow-Ups:
- Re: Ignore SQL Server 2000 store proc errors and still get results?
- From: Mike Jansen
- Re: Ignore SQL Server 2000 store proc errors and still get results?
- References:
- Ignore SQL Server 2000 store proc errors and still get results?
- From: Mike Jansen
- Ignore SQL Server 2000 store proc errors and still get results?
- Prev by Date: Using identity_insert in a stopred procedure with a variable
- Next by Date: Re: typed dataset question
- Previous by thread: Re: Ignore SQL Server 2000 store proc errors and still get results?
- Next by thread: Re: Ignore SQL Server 2000 store proc errors and still get results?
- Index(es):
Relevant Pages
|
Loading