Hi,
I'm seeing some strang behaviour with SSIS 2012 concerning calling child packages from a main package.
First let me set the scene: I have several packages loading data. Next to that I also have a master package that reads a table that contains all the names and path's of the different packages to execute. Reading the packagenames works, dynamically calling the packages is no problem, so everthing works, BUT performance is not as I would expect it to be.
Let me explain: When executing a single package from SS Data tools it takes only a few seconds. When I run my master package in ss data tools and call that same package it can take up to 2 minutes to complete succesfully. When I execute the same master package from command prompt with DTEXEC the same child package executes again in only a few seconds.
Anyone any idea's why executing master package in design is that slow, while executing the child package in design, or executing the master package from command prompt is fast?
I have a send problem that I'm still investigating but any tips would be welcome: I want to execute these master packages from a job in SQL Server. Normally I would use the integration services step, but for my first master I need to pass a password to the package so I choose to use Operating System step type. When I execute the dtexec in command prompt (using the same user as the sql server agent account) it works fine. But when I execute the job with exactly the same command it seems to be doing nothing, while the job states that it is executing. (The master pacakge is executed, but the child package isn't started. This is what I get from my logging information I added to the packages)
Regards,
Nico