• opc.three (4/23/2013)


    The point is, using xp_cmdshell limits your options. It paints you into a corner. PowerShell has 100% functionality coverage, and infinitely more, over CmdShell. And when run separate from SQL Server we are afforded so many more options from an auditing and security standpoint it's really no contest, really, no contest. How anyone could continue to argue the contrary is beyond me.

    Heh... it hasn't painted me into any corner. I can do everything I need to do with files in a flexible and easy to do manner using the "old" ways.

    You keep talking about all of the options for auditing for PowerShell. What are they, how do you implement them, and why are they any different that auditing DOS commands? And so far as security goes, what exactly is the advantage of PowerShell over, say, using a DOS DEL command operated from the Command Prompt?

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