Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cronid
Starting Member
26 Posts |
 Posted - 2006-11-02 : 09:10:40
|
| I have a package where the first step archives a file if it is present. Most times it should not be present, so I have set the workflow for the next step to be on completion. This works fine for the package, the subsequent steps are always executed as I intended. Unfortunately, the job shows as a failure most days when the file is not present.Is there a way to set up the job (or package) so that the results of this first step (failure or success) do not impact the job status (failure or success)? |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-11-02 : 10:14:13
|
| By archive do you mean move the file to another directory?Just use an os move command which should show successful whether or not the file is present.Otherwise add a step to check to see if the file exists and then only execute the archive step if it does exist.or use an ectivex script and the fso as inhttp://www.nigelrivett.net/DTS/DTSActivexFileExists.html==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
code for job success on step failure