Jeff Moden (12/18/2013)
Nice trick. It's also another notch on a 2x4 list of reasons why I try to do everything in T-SQL. ;-)
Yeah, yeah, my favorite Luddite.
Considering I avoid child packages in general like the plague, I don't run into this very often. I find them to offer little assistance, as you can rarely modularize a child package well enough for multiple inheritance of over 3 packages (my minimum for when I look to standardize code calls in just about everything). SSIS shouldn't be treated like standard coding where you're typically trying to pass information between multiple component functions off a MAIN() or whatever.
SSIS however is awesome for laying out processing methodology and calling sequential procedures with obvious and self-documenting logic pathing, however. There's plenty of other things it can do but I find a single package controlling a complete task to be very easy to read without having to dig through code to find the control pass points or dig through signficantly complex if trees. There's also places where it's faster than T-SQL (small lookup lists come to mind) if your transforming across servers.
And now I sound like a brochure. No more after midnight typing for me. Bedtime!
- Craig Farrell
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake. For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally TablesTwitter: @AnyWayDBA