J
Jeff Jarrell
I know this may be a sql thing but I would expect someone to have dealt with
this.
I have some update stored procedures with many steps. normally, my stored
procedures "set nocount off".
so the rowsAffected = ExecuteNonQuery doesn't return anything but 0. So I
turn it on (nocount off), but it is very easy to mess up what step has the
nocount on\off (as time goes on, changes, etc) . The proper "Rows Affected"
might be the first step, might be the last step, might be somewhere in
between.
In my stored procedure I'd like to capture the row's affected in the right
step, and then force the proper return at the end of the stored procedure.
Any ideas on this?
thanks,
jeff
this.
I have some update stored procedures with many steps. normally, my stored
procedures "set nocount off".
so the rowsAffected = ExecuteNonQuery doesn't return anything but 0. So I
turn it on (nocount off), but it is very easy to mess up what step has the
nocount on\off (as time goes on, changes, etc) . The proper "Rows Affected"
might be the first step, might be the last step, might be somewhere in
between.
In my stored procedure I'd like to capture the row's affected in the right
step, and then force the proper return at the end of the stored procedure.
Any ideas on this?
thanks,
jeff