• Jeff Moden (4/29/2013)


    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. 😉

    I guess so, unless you consider xp_cmdshell nothing. No free lunch Jeff.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato