Hi All,
First of all, I have to say I'm pretty new to SSIS in SQL 2014... Not to SSIS but to the 2014 version.
I currently experience a very strange behaviour at one of my clients. I had to migrate an SSIS project from 2008R2 to 2014 and converted it to project deployment model to make use of the "new" functionality. The project contains several packages, however, one is the main package which calls and executes the other packages. This works fine in 2008R2.
Now, in 2014, the tasks in subpackages are not failing in case of an error. Instead, the task keeps running forever, even though it can't succeed. When I start the subpackage directly, everything works fine (fails in case of failure).
To make it a bit clearer:
I have two packages:
ParentPackage
ChildPackage
ParentPackage calls ChildPackage, ChildPackage contains a simple SQL tasks which calls stored procedure SP1.
If I run ChildPackage (from SQL Agent or directly in SSDT), SP1 gets executed, ChildPackage succeeds (good)
If I run ParentPackage, ChildPackage is executed, SP1 is executed, ChildPackage succeeds. (good)
Now, If I change the SQL Tasks to call SP2, which doesnt exist, the following happens:
If I run ChildPackage, SP2 cannot be executed, SQL Task fails, ChildPackage fails (which is what I expect)
If I run ParentPackage, ChildPackage is executed, SQL Task is executed but keeps in running state (as SP2 doesn't exist), ChildPackage als stays in running state.
In the last case, I expect the SQL Task to fail and not to keep running.
Does anyone have an idea what I'm doing wrong? Why isn't the SQL Task failing?
Thanks,
Pascal