SQL Task Error in proc not detected?

eric_mamet_test_at_yahoo.co.uk
Date: 02/07/05 

Date: 7 Feb 2005 09:45:08 -0800

I have a package calling a stored proc PROC1, itself calling another
proc PROC2, calling a third proc PROC3.

Each procedure returns -1 on success and 0 on error
Each Procedure raises a raiserror('adhoc message',16,1) on error

Something goes wrong in PROC3 which is detected by PROC2 (through
@@ERROR)
PROC2 raises and error and return 0
PROC1 detects the problem (because of returned 0) and raises an error
itself.

The SQL Task does not seem to notice the error and carries on as if
everything was fine...

Question: what could make this SQL Task ignore the error?

Usually, my errors are triggered by a procedure at level 2, not 3, and
DTS detects the error properly.

Thanks for your help!

Eric

Relevant Pages

  • Re: Passing a named function instead of a code block?
    ... grab a method as an object without calling it, ... :square1 is an atomic unit representing the symbol whose ... we call square1 and cast the result of that using '&'. ... '&square2' is fine as square2 is just a variable referring to a proc. ...
    (comp.lang.ruby)
  • Re: Using output variables
    ... The problem lies in the Web page that calling ... DECLARE @permission int ... EXEC GetPermissions @PID,@UserID,@permission OUTPUT ... > I have the Page calling the stored proc and the proc ...
    (microsoft.public.sqlserver.programming)
  • Re: Clearing the pending results
    ... First, how are you calling this, with a cmd.Executexxx method? ... .NextResult three times, then your while dr.Read(0 will reference the last ... proc definitions...I'd mainly need to know about what the procs are ... > I have a stored procedure. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Yield should be renamed call_block
    ... less overhead in yielding than in calling a free-standing proc). ... can't reimplement yield in Ruby with the reflection it offers right ...
    (comp.lang.ruby)
  • Re: Table Locking
    ... "Thomas" wrote in message ... > I mean locking the entire table, till the end of the running of the procedure, I am calling some other procedure within this proc. ...
    (microsoft.public.sqlserver.programming)