Execution Patterns - SQL Server Integration Services Design Patterns - page 82

ment model. Figure 2-8 shows the Execute Package task configured to execute the
Chapter2.dtsx package.
Figure 2-8 . Selecting the Project Reference Package
You can close the editor after selecting the package. Test it by executing Paren-
t2.dtsx in the SSIS debugger.
METADATA-DRIVEN EXECUTION
I have used all of the methods for SSIS package execution listed in this chapter.
They each have advantages and disadvantages. How then, do you select which
method to use? That is an excellent question and I'm glad you asked! I consider
the following:
• Troubleshooting: At some time in the future, someone will have to fig-
ure out why a package failed to execute. Facilitating troubleshooting is
not something to be tacked onto the end of a data integration develop-
ment project; you need to consider it up front. It is as important as se-
curity. I select an SSIS package execution method that supports
troubleshooting in each enterprise.
• Code maintenance: The SSIS project will possibly be modified in the
future. This means the packages, projects, and execution methodology
need to be documented. It also means I need to consider the skills and
comfort levels of the individuals or team maintaining this code. If the
individuals or team are skilled .NET developers, I lean toward using the
Script task and component for complex operations. I also attempt to de-