Building Custom Tasks for SQL Server Integration Services, 2nd Edition is Available

Update: Please be sure to read Building Custom Tasks for SSIS Second Edition Errata, Chapters 1-9 for important updates to the demo code.

I am honored, humbled, and excited to announce the release of Building Custom Tasks for SQL Server Integration Services, 2nd Edition!

In the first edition of this book, the demo task is the Execute Catalog Package Task, or ECPT. I can hear you thinking,…

“Andy, doesn’t SSIS ship with an Execute Package Task already?”

Yes. Yes it does.

“So why build a new one?”

That’s an excellent question. I’m so glad you asked!

The Execute Package Task that ships with SSIS permits SSIS developers to execute another SSIS package. The “calling” package is often referred to as the “parent” and the “called” package is often referred to as the “child.” To paraphrase Henry Ford, you can call any SSIS package you want, as long as the SSIS package you want to call is in the same SSIS project.

More…

The Execute Catalog Package Task

ECPT permits calling an SSIS package in any SSIS project.
ECPT permits calling an SSIS package in any SSIS project in any SSIS Folder.
ECPT permits calling an SSIS package in any SSIS project in any SSIS Folder on any SSIS Catalog.

Azure-SSIS Integration Runtime for Azure Data Factory

ECPT permits calling an SSIS package deployed to Azure SSIS Integration Runtime Catalogs that are part of Azure Data Factory.

You may use ECPT to execute SSIS packages deployed to on-premises SSIS Catalogs.
You may use ECPT to execute SSIS packages deployed to Azure-SSIS IR Catalogs.

An on-premises parent package can actually execute SSIS packages stored in both on-premises and Azure-SSIS IR Catalogs.

A parent package deployed to an Azure-SSIS IR may execute SSIS packages in that Azure-SSIS IR.

I forgot to mention one important part: The book covers how to create an MSI installer for the ECPT for distribution onto other on-premises SSIS servers, and then how to deploy the ECPT to Azure-SSIS nodes.

“SSIS-y”

A more "SSIS-y" Execute Catalog Package Task Editor

In the second edition, I converted the VB code to C#, and then expanded the editor development to include (what I describe as) a more “SSIS-y” editor.

Catch Me On The ‘Tube

Click to visit my YouTube channel!

YouTube, that is.

In coming weeks, I will be demonstrating the code in the book.

To be notified of my live stream events, visit my YouTube channel, click subscribe, and then click the bell and click “All” to be notified when I start a live stream.

Click to visit my YouTube channel!

If YouTube is not your thing, you may also follow me on Twitch and / or LinkedIn.

Click to visit my Twitch channel!   Click to visit my LinkedIn profile!

Want More?

Drop me a line. I’d love to hear your suggestions, feedback, and thoughts.

Caveat

The SSIS Catalog will change.
When the SSIS Catalog changes, the code in this book will break.
To keep up, please subscribe to my newsletter, channels, or both. I promise to do my best to keep you updated.

Conclusion

Readers of the first edition built some really cool custom SSIS tasks! I’m excited to see what you build next!

:{>

Andy Leonard

andyleonard.blog

Christian, husband, dad, grandpa, Data Philosopher, Data Engineer, SSIS and Biml guy. I was cloud before cloud was cool. :{>

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.