Stored Procedure Development Query

  • I have one Main Stored Procedure.

    I will be executing multiple stored procedure one by one. I would like to continue processing even in case one of the procedure was aborted due to Error.

    How can I achieve this objective?

  • It depends on the severity of the error. Higher severity errors cause a disconnect of the offending process. Those cannot be trapped.

    For the other procedures, in SQL Server 2005, you can use TRY/CATCH constructs to get the job done. This is an introduction to the topic[/url], but there's a lot more to learn.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply