![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a number of DTS packages that execute over night to sent spreadsheets to offices around the globe. The spreadsheet shows what has changed in the area of the database that the office is concerned with. The first step in the DTS package is to count the number of changes, if it is Zero an activeX package reports failure and the package is halted. The problem is when I check that everything is working the job shows that it failed. I have tried putting all sorts of dummy steps after the failure but SQL Server Agent still reports the job as a failure becuase one step failed. Does anybody have any fixes? Many Thanks Mike |
#3
| |||
| |||
|
|
Don't fail the task, use a workflow script instead. An example of this concept is shown here- How can I check if a file exists? (http://www.sqldts.com/default.aspx?211) -- Darren Green http://www.sqldts.com "Mike T" <mike (AT) trebilcock (DOT) net> wrote in message news:uXG1kD41EHA.2292 (AT) TK2MSFTNGP15 (DOT) phx.gbl... I have a number of DTS packages that execute over night to sent spreadsheets to offices around the globe. The spreadsheet shows what has changed in the area of the database that the office is concerned with. The first step in the DTS package is to count the number of changes, if it is Zero an activeX package reports failure and the package is halted. The problem is when I check that everything is working the job shows that it failed. I have tried putting all sorts of dummy steps after the failure but SQL Server Agent still reports the job as a failure becuase one step failed. Does anybody have any fixes? Many Thanks Mike |
![]() |
| Thread Tools | |
| Display Modes | |
| |