| GeoSynch 2005-08-30, 3:25 am |
| Try removing
SET NOCOUNT ON
from the stored procedure.
GeoSynch
"Dimitri Furman" <dfurman@cloud99.net> wrote in message
news:Xns96C19F85E9F5
6dfurmancloud99@127.0.0.1...
> SQL Server 2000 SP3.
>
> Is it possible for the @@ROWCOUNT function to return NULL after a
> statement? I am troubleshooting a relatively large stored procedure with
> multiple SELECT statements and a couple of INSERTs into table variables.
> Immediately after each statement I save the value returned by @@ROWCOUNT to
> a local variable. That information eventually is passed back to the client
> via one output parameter, for all statements in the procedure.
> Occasionally, the value returned via that parameter is NULL. This cannot be
> reproduced by re-running the SP with the same input parameters.
>
> Before doing any further troubleshooting, I would like to rule out the
> possibility that @@ROWCOUNT can actually return a NULL under some
> circumstances. From searching the archives, it appears that in SQL Server
> 7.0 this could happen in the context of a DML query on a table with
> triggers. This is not the case here - the only DML queries are INSERTs into
> table variables, all other queries in the SP are SELECTs.
>
> Any related information would be appreciated.
>
> --
> remove a 9 to reply by email
|