• Sean Lange (10/15/2013)


    If you got your quote correct that person is moron.

    Heh... if the quote is correct, then that "DBA" is more off than on, so stop insulting morons. He's clearly a moroff. 😀

    The one thing that I do agree with is...

    ... if there are no special error messages required and

    ... if all you're going to do in the CATCH block is rethrow the same error and

    ... if you don't need redirection of special handling on an error

    ... then there's usually no need for Try/Catch blocks in a stored procedure. Let SQL Server do what it was designed to do. If you need multiple commands in a stored procedure to act as an "all or nothing" unit, the using explicit transactions with SET XACT_ABORT ON is usually enough for a lot of people.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)