Home Forums SQL Server 2005 Development Suppressing output from a stored procedure. RE: Suppressing output from a stored procedure.

  • April 29, 2013 at 12:56 pm

    #1610964

    opc.three (4/26/2013)

    A proper solution would be to get rid of the use of xp_cmdshell all together.

    The recommended way using either a SQL Agent job or a web service that invokes the package. Both are decoupled from the caller, which is how it should be:

    Loading and Running a Remote Package Programmatically

    Heh... so far as I'm concerned, the "proper" way would be to get rid of the SSIS package and do it in TSQL. No call to anything required for that. 😉

    --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)