Update: If you are using the SSIS Catalog found in SSIS 2012 and later versions, you may be interested in the SSIS Framework Community Edition, an open source, Catalog-integrated execution framework.
In preparation for SQL Saturday #84 – Kalamazoo, SQLBits 9, and the PASS Summit 2011; I’ve been honing my presentation called Designing an SSIS Framework. I delivered this presentation a few times over the past couple months. Each time, I promised the attendees I’d send them the code if they emailed me… and a couple things got in the way:
First, a lot of people requested the presentation. Second, I got really busy! Both of those beat their respective alternatives.
I finished building and barely testing the code this evening. You can grab an updated copy here. The zip file contains the SSIS 2008 R2 solution and two other folders: Config and Sql. Config holds a configuration file that points to a database named SSISConfig on the default instance of your local workstation or server (edit SSISConfigParent.dtsConfig if you want to change this location).
To make it all work dynamically, you need to create a System Environment Variable named SSISConfig (case-sensitive) and set the value to the full path of SSISConfigParent.dtsConfig on your workstation or server. Next, run the “Create SSISConfig.sql” script in the Sql folder, followed by the “Add An SSIS Applications.sql” script (edited to reflect the folder that contains the SSIS packages on your workstation or server). This should get everything ready for the SSISConfig SSIS solution. When you execute Parent.dtsx, it should call Template1.dtsx, then Template2.dtsx, and finally ErrorTest.dtsx.
Let me know how it goes!
Recording: Introducing SSIS Framework Community Edition
Enterprise Data & Analytics is here to help! Contact us today.