Posted by Erland Sommarskog on 07/11/06 21:20

(timothy.alvis@gmail.com) writes:
> It's not so much a problem, as I don't know how to get around this
> issue. We have applications that rely on the return value of a stored
> procedure. This stored procedure inserts a record into a table that has
> a trigger. The trigger calls a couple of stored procedures itself.
>
> Due to the trigger, we have a return value of 0 coming in ahead of the
> return value for the stored procedure we call directly. I've tested
> this in Query Analyzer as well, and the same behavior applies.
>
> In case I didn't describe it clearly:
>
> Call storedproc1
>
> storedproc1 inserts a record into table1
>
> table1 has an INSERT trigger
>
> expected behavior is: storedproc1 returns value1 and value2
>
> actual behavior is: storedproc1 returns 0, then returns value 1 and
> value 2

Returns? This needs some clarification. A stored procedure can return
data in three different ways:
o Result set
o Output parameters
o Return value. as in EXEC @ret = some_sp

Which do you mean?

Overall, it would help if you posted the code of the procedure, so we know
what you are talking about. Please also include the output when run the
procedure in Query Analyzer.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]