December 9, 2008 at 5:15 pm
Hi Mark,
I've witnessed similar behavior. Although I don't know why it happens, I've seen child packages open and not appear to run until the next child package opens (and not appear to run)...
Most of the time it works ok for me if the child packages called from the parent are called from the files in the same solution. In other words, the parent isn't calling packages stored in SQL Server, or from some other file location - it's calling the child packages in the solution I now have open. Sometimes this isn't optimal (like in an SSIS framework - you wouldn't want to add all the children to your framework project!).
I'm not sure if this helps or not, but you're not alone...
:{> Andy
Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics
December 10, 2008 at 8:15 am
Thanks Andy I was beginning to feel as if I were alone on this one. Your explanation is simular to my situation because my parent package is calling the child packages in a different file location. I am fairly new to SSIS but the original designer of the package I believe was attempting to creae a dev and production environment and that is the reason for the different locations. The parent package in dev needed to point to the production child packages as the mapping is being done dynamically. He does have a copy of the production parent package in the same location as the child packages maybe I should be running this one instead of my dev one.
Appreciate the insight Andy.
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply