Parent-Child Patterns - SQL Server Integration Services Design Patterns - page 388

CHAPTER 16
Parent-Child Patterns
In earlier versions of Integration Services, the data movement platform did not include a
management framework, which is the implementation of the execution, logging, and de-
ployment of the Integration Services packages. To try to fill this hole, developers created
their own management framework to use in their organizations. As with any custom
solution, the developers found that the management framework needed to be cared for
and upgraded when new versions or new packages were introduced into the system.
Previous chapters have covered ETL instrumentation, focusing on metadata collec-
tion and validation. The metadata we discussed included key information you need to
manage your packages. This chapter covers parent-child patterns, where an Integration
Services package can execute another package from within its own execution. These
patterns are a critical part of implementing an ETL framework.
Integration Services 2014 contains its own management framework, which includes
logging and execution through the SSIS Catalog. In this and subsequent chapters, we
will show you how to use the available framework and enhance it to provide more in-
formation while still working around the issues we discuss.
The following are the three parent-child patterns we'll cover in this chapter:
• The master package pattern
• The dynamic child package pattern
• The child-to-parent variable pattern
Using these patterns, you can implement the Integration Services management func-
tionality out of the box.