Same client - New Project!
I’m really excited about a new project that I am just now beginning. I recently finished an addition to a data warehouse (glad I still remember how since it’s been almost five years since I’ve worked on one) and am now going to build a set of ‘generic’ SSIS packages to load it. This is going to be interesting because the client has multiple locations worldwide. Rather than create 10, 20, or 75 SSIS packages (several per country) they want to deploy a single-use package concept handle similar tasks for all countries. So, I’ll be working on basically three packages: 1) to extract from DB2, 2) to import the .txt files, and 3) to fire off remaining procedures and processes. I imagine that I will be programming SSIS i.e. using the programming model to create a dynamic package in c#.
This is a good idea, ‘genericizing’ packages, and I’m all for it. Much easier to manage down the road and a lot less code to maintain. Remember my post on custom assemblies as a replacement for c# or vb.net code in script tasks scattered all over the place? Same deal here – write once (methods, events, error handling, logging, reporting, etc.) for SSIS and use everywhere. Crack a lackin!!!
Look for a lot of great SSIS 2008 stuff coming down the pike.
Lee
--------------------------
‘“He was the meanest guy to ever come down the pike” Fine. What about guys who come up the pike? Not everyone lives north of the pike! Some guys come up the pike, and they’re really mean’
The late George Carlin
d27f9cfc-53d6-4ded-bcc1-f4250ab4c444|0|.0