Instead of executing these DTS packages individually, I have decided to create a 'parent' DTS package that will fire off each of the five 'child' DTS packages using 'On Success' precedences.
This seemed like a pretty straight forward task, but when one of the child DTS packages fails, the 'parent' DTS package continues to execute the next 'child' DTS package through the 'On Success' precedence. I was expecting the 'parent' DTS to fire off an 'on failure' precendence and stop executing
Can anyone tell me why the 'parent' DTS package continues with the 'on success' precedence after one of the 'child' DTS packages has failed.
I can't answer your question directly however I tend to use the below to execute my DTSs from code. I now include about as little as possible in my DTSs (the transformation only in fact) and wrap everything else up in a sproc.
So - the long and the short of my answer would be - perhaps look at replacing your masater DTS with some T-SQL code - makes trouble shooting and execution flow much easier IMHO. http://www.pengoworks.com/index.cfm?...s:spExecuteDTS
Thanks for the swift response Pootle Flump - much appreciated.
I did a bit of digging and found this in the SQL Server 2005 books online. I probably should have said that we are running SQL Server 2000.
Alternatively, sometimes you want the parent and child packages to fail together as one unit, or you might not want to incur the additional overhead of another process. For example, if a child process fails and subsequent processing in the parent process of the package depends on success of the child process, the child package should run in the process of the parent package.
By default, the ExecuteOutOfProcess property of the Execute Package task is set to False, and the child package runs in the same process as the parent package. If you set this property to True, you can debug only packages that contain limited functionality. To debug all packages supported by your edition of SQL Server 2005, you must install Integration Services.
Does anyone know if it is possible to set the ExecuteOutOfProcess property on SQL Server 2000, or is this specific to SQL Server 2005?