I had to import and process 100+ files for my latest project and wondered if there was a way to generate SSIS packages based on a repository table containing the rules. As it turns out, this can be done but the programming model is a bit awkward.
The samples that you can find online are not allways functional and debugging is difficult. I did get it to work though and will show you how I did it and what problems I ran into.
After this session you will know how to generate packages that contain sources, destinations, cached lookups, derived columns, conditional splits, sorts, union all, etc.
This session is not about the script component inside SSIS but about generating SSIS packages and programmatically reading and changing properties of existing packages.This session should also be usefull if you're not a full blown developer but more of a DBA type. I'm a DBA and I got through this :-)
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