Satheesh E.P. (4/1/2014)
XP_cmdshell is working fine in our environment with a non-sysadmin account.
I don't know about your specific problem but I have to tell you that giving a non-sysadmin account privs to execute xp_CmdShell directly is one of the worst things for security that you could ever do. You should have the user only have the privs to run a protected stored procedure that runs xp_CmdShell in a safe and limited manner.
It's for things like this that xp_CmdShell has gotten such a bad name. ;-)
is pronounced ree-bar and is a Modenism for R
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.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs