From the Article
The problem is [font="Arial Black"]there are over 300 individual child SSIS packages [/font]that ......{snip}...
For bigger ETL setups with many of packages and tasks, you might need a system that loops through all your packages to obtain this information. For instance you can loop through the .dtsx files with XML or use C# or VB and the SISS object Model to achieve this objective, [font="Arial Black"]a topic I will leave for another discussion[/font].
Good article but I'm really hoping that "another discussion" will be one of the two other parts of this series because something that does the above is really going to be important to someone who has "over 300 individual child SSIS packages".
--Jeff Moden
Change is inevitable... Change for the better is not.