Database Reference
In-Depth Information
Delete @PackageTbl
Commit
The T-SQL in Listing 2-8 builds a simple SSIS application in the execution frame-
work. It calls our Chapter2.dtsx SSIS package twice. If you return to SSDT-BI
and execute the parent package, you will note the Chapter2.dtsx SSIS package
executes twice in quick succession. You can see that execution in Figure 2-4 .
Figure 2-4 . Chapter2.dtsx executing twice without waiting
It is important to understand that the framework is a “fire and forget” design. The
screenshot in Figure 2-4 shows both instances of Chapter2.dtsx showing their re-
spective message boxes, yet the tasks in the background have completed. This ap-
proach works well if your SSIS packages can be executed in parallel. But what if there
are dependencies between packages? This framework does not facilitate dependent
package execution, but I will show you a way to couple the framework with the SQL
Server Agent Job scheduler in the next section. Coupling will allow you to execute the
parent package for each “step” of a process, calling an SSIS application each step, and
in turn, calling one or more SSIS packages in parallel.
 
 
Search WWH ::




Custom Search