sqlfriends (4/1/2013)
Grant Fritchey (4/1/2013)
Glad to hear it's fixed.Just curious though, why not use a PowerShell type of step in SQL Agent for a PowerShell script?
I found it runs much faster using cmdexe type vs powshell type to run the jobs.
I read an article telling what is the difference , it seems they are using different powershell module to run the job. I cannot find the article now by doing some search.
For my cases, I can use both, but it takes much shorter time for using cmdexec to trigger the job and finish the job.
🙂
Shifting gears, do you have any auditing in place to audit your PowerShell runs at the OS Level? Has nothing to do with your current problem. I'm just curious. Thanks for any feedback on this.
--Jeff Moden
Change is inevitable... Change for the better is not.