The source code for the version of the Execute Catalog Package Task we built is available here from the DILM Suite web site, and it’s free. You can also access the code from this book’s catalog page on the Apress web site ( www.apress.com/978-1-4842-2932-2 ).

FormalPara Caution

The Demo code is not production code!

I’ve placed several this-is-not-production-code warnings throughout the book because, well, this is not production code. What would I do to make my example code into production code? That’s a great question, and following is my take on answering it:

  1. 1.

    Error handling : Try-catch is completely missing from the sample code. Also missing is validation logic.

  2. 2.

    Features : Executing an SSIS package in the catalog usually involves more than just starting the package. Package execution can be customized and parameterized in a number of ways, including running in 32-bit, executing synchronously, using different logging levels, and using references—just to name a few.

  3. 3.

    Installer: In my opinion, Production-grade code should include an installation process that wraps the code in either a setup.exe or *.msi file. I usually add the installer project to the code project(s) so that the installer is source-controlled with the code project(s).

Kudos to Microsoft for providing developers with the ability to build custom SSIS (SQL Server Integration Services) tasks in Visual Studio Community Edition! I hope you have enjoyed reading this material as much as I enjoyed creating it.

As always, I welcome feedback, suggestions, and comments.