Hi all,
Here's my scenario:
I have a DTS package with 8 separate steps. This DTS package drops and recreates a table, then fills the table with a bunch of data, and eventually updates a table in a linked oracle server with the collected data.
We are running this DTS package with a scheduled job, which runs nightly. The job has three steps: 1) executes the DTS package, 2) writes a record in an "exitstatus" table if step 1 executes successfully indicated it completed successfully, and 3) writes a record in the "exitstatus" table if step 1 fails, indicating a failure occurred.
Then we have a process that checks the exitstatus table to determine whether or not any failures occurred overnight. I'm sure this is not the best method, but it's been around here for a long time and it's what we need to work with for now.
My question is: is there a way to capture the specific error that occurred to force the DTS package (and therefore step 1 in the job) to fail? All we find out is that it failed - we never are able to determine at which step the DTS package failed, or why it failed. We would want to store the error in the exitstatus table.
Any help would be greatly appreciated.
Thanks!
Cory
*cLFlaVA
----------------------------
[tt]( <P> <B>)13 * (<P> <.</B>)[/tt]
[URL unfurl="true"]http://www.coryarthus.com/[/url]
Here's my scenario:
I have a DTS package with 8 separate steps. This DTS package drops and recreates a table, then fills the table with a bunch of data, and eventually updates a table in a linked oracle server with the collected data.
We are running this DTS package with a scheduled job, which runs nightly. The job has three steps: 1) executes the DTS package, 2) writes a record in an "exitstatus" table if step 1 executes successfully indicated it completed successfully, and 3) writes a record in the "exitstatus" table if step 1 fails, indicating a failure occurred.
Then we have a process that checks the exitstatus table to determine whether or not any failures occurred overnight. I'm sure this is not the best method, but it's been around here for a long time and it's what we need to work with for now.
My question is: is there a way to capture the specific error that occurred to force the DTS package (and therefore step 1 in the job) to fail? All we find out is that it failed - we never are able to determine at which step the DTS package failed, or why it failed. We would want to store the error in the exitstatus table.
Any help would be greatly appreciated.
Thanks!
Cory
*cLFlaVA
----------------------------
[tt]( <P> <B>)13 * (<P> <.</B>)[/tt]
[URL unfurl="true"]http://www.coryarthus.com/[/url]