Replacement of xp_cmdshell

  • Hi

    I have scheduled a job which has step which calls exe.

    I have used xp_cmdshell to execute the exe.

    But i have observed that the exe does not gets kill when it finishes its task rather i have to manually kill the exe.

    But the same exe when i run through SSIS package it gets killed.

    However im analysing SSIS pacakage but i dont want to use SSIS pacakage and stick to JOB to save performance.

    Also i think xp_cmdshell takes the maximum time and memory. Can someone suggest why. Also can I replace xp_cmdshell with some other command so that the exe is executed and in less time

  • Why aren't you just using an OS Command line step in your job to run the executable? There really is no need to use T-SQL and xp_cmdshell to do that.

  • Lynn Pettis (12/19/2008)


    Why aren't you just using an OS Command line step in your job to run the executable? There really is no need to use T-SQL and xp_cmdshell to do that.

    Can you please tell me how can I write one.

  • When you create the job step, set the type to OS command. They type in the OS commands that you need.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 4 posts - 1 through 3 (of 3 total)

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