ETL shootout-SSIS vs Powershell
I know what you're thinking, Powershell is not an ETL tool. And you're probably right. But I keep running into weird requests that were just easier to fix with Powershell. I'll show you why some things are not easy in SSIS. I'll also discuss how you can work around a lot of that instead of switching to Powershell like I did. This session will be around 70% "why is this hard in SSIS and can you work around it?" and 30% "Look how cool Powershell is"
I’m a SQL Server consultant based in the Netherlands. I’m a SQL Server MVP and I’m the co-founder and current chairman of the Dutch PASS Chapter and a member of the volunteer team for the Dutch SQL Saturday’s. I’ve done a whole lot of pure DBA work managing 100′s of servers and learning something new every day.
These days I spend a lot of time on just a few servers containing some large databases and the better part of the day is spent with SSIS. In both roles I’ve been using Powershell a lot. I joke sometimes that I replaced myself with a powershell script when leaving the DBA role, but these days I automate so much that I have to watch myself and not actually do just that