LinkedIn | FaceBook | Twitter
Today was the final day of the conference, but I had a packed house for our discussion on PowerShell and SQL Server. I wanted to blog about one concept I covered in the demo: Why would I use PowerShell when I have SSIS, stored procs, batch files and other mechanisms?
I submit the following reasons:
OK - go off and try it. It isn't hard, it works well, and it makes your work easer.
PingBack from http://mstechnews.info/2008/11/pass-2008-conference-day-five/
This presentation was one of the highlights of the conference to me. Great combination of laughs and information. Your co-presenter's one word answers to the audience questions were all-time classics.
If your company is like mine, you are largely at the mercy of your software vendors as to when you'll
All the buzz over Windows PowerShell has aroused my curiosity, but it's hard to justify spending
I've done a comparison of the SSIS and Powershell pipelines here if you're interested
Talking Pipelines : SSIS and Powershell
Buck, the link for the download isn't working, and you might want to put up a 404 redirect as I'm getting a page that looks like your site has been taken over by a link farm.
I've been wanting to get PowerShell working for me, but ran in to problems with certificate requirements blocking me from accessing servers remotely via PowerShell, so I'm sticking with Perl for now and looking in to Rodney Landrum's DBA Repository system.