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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Errorhandling in Jobs, without quit

Author  Topic 

spastic
Starting Member

3 Posts

Posted - 2003-03-21 : 05:35:30
Hi ..

I Have a Job wich is calling a SP. this SP calls a second SP. This second SP could produce a failure (in a while-loop from a cursor).
If SQL-Server raises the failure, it stops the job (Quit with failure OR Quit with Succeed). But I don't want the job to quit. It should go on with next even if there are failures.

can you help me?

spastic

tacket
Starting Member

47 Posts

Posted - 2003-03-26 : 09:52:26
I would create a DTS package and separate the code so that SP1 will complete and then after it's completion you can do an 'On Completion' step and then call SP2. Then if you need to do something else after SP2, just do another 'On Completion' step.

This may require some rewriting of the SP's.


Phil

Go to Top of Page

Page47
Master Smack Fu Yak Hacker

2878 Posts

Posted - 2003-03-26 : 11:07:25
Alter your On success / failure flow for the job step such that the on failure action is Goto the next step.

Jay White
{0}
Go to Top of Page

spastic
Starting Member

3 Posts

Posted - 2003-04-01 : 07:27:34
The DTS package works.. without changing the code. The behavior, when executing a SP is the same as executing the SP in the query analyzer. It tells me that there are error, but it doesn't stop. and that was what I wanted. thanks a lot.
quote:

I would create a DTS package and separate the code so that SP1 will complete and then after it's completion you can do an 'On Completion' step and then call SP2. Then if you need to do something else after SP2, just do another 'On Completion' step.

This may require some rewriting of the SP's.


Phil





Go to Top of Page

spastic
Starting Member

3 Posts

Posted - 2003-04-01 : 07:29:36
That can not work, because the 2.SP is called a lot of times within the 1. SP in a loop. I got the solution.. thanks.

quote:

Alter your On success / failure flow for the job step such that the on failure action is Goto the next step.

Jay White
{0}



Go to Top of Page
   

- Advertisement -