May 10, 2006 at 4:09 am
Hello,
I've a stored procedure which backups all databases (about 900). This stored procedure works fine with queryanalyzer (some errors appear f.e. db 150 is suspect)
The problem is, when starting that sp within a job, the job will quit at db 150. Is it possible to 'tell' the job to continue also when error raised ?
Also I've read about
SET XACT_ABORT OFF
but there's no effect.
Best regards,
Michael
May 15, 2006 at 11:04 am
So far I haven't had that problem if I set the job step to proceed to another step on failure, like an emailing step or something.
If the retries for the step is zero and the "On Faliure" option is set to quit the job reporting failure then I'd expect to see what you reported.
hth
Skål - jh
May 16, 2006 at 2:27 am
Thank you for your answer.
I've solved the problem by using a 'normal' win-schedulled task, which starts the SQLCMD.EXE with the wanted sp-call as parameter.
thx.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply