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

Dts.Variables("User::ChildFileName").Value
= "SalesFile.txt"
Once you run it, the package will finish with the figure seen in Figure 16-8 .
Figure 16-8 . Child-to-parent variable pattern execution
The passing of variable values from child to parent suceeds because of how con-
tainers work in Integration Services. Inside of a package, any child container, such as a
Sequence container, can access its parent's properties. Likewise, any child task, such as
an Execute SQL task, can access its parent's properties. This paradigm allows you to
use variables and properties without having to re-create them for every object in your
package. When you add a child package using the Execute Package task, you add an-
other layer to the parent-child hierarchy and allow the child package to set the parent
package's variable.
Conclusion
SQL Server enthusiasts everywhere embraced Integration Services when it was first in-
troduced as part of SQL Server 2005. The latest edition of Integration Services has
been enhanced to make ETL developers even more excited than before. Integration