Hi all,

I had a perfectly fine working stored procedure. In order to increase it's performance I put set nocount on in it. After that I started to encounter an error message.

"p_ABC stored procedure attempted to return a status of null, which is not allowed, a status of 0 will be returned instead."

p_ABC stored procedure is being called inside main stored procedure in which I have put set nocount on statement. By the way if I remove
set nocount on, everything starts to work fine again.

My question is "Is this predicatable behaviour of set nocount on statement and is documented already?". Reply to this question would really help me to remove my confusion over the issue.

Thanks in advance,
Puneet Mittal






Puneet

Could u send ur SP's Code. Maybe u have changed the code, its strange.

Always:),
Hovik Melkomian.

Hello,

I've never had any problems setting set nocount on in my stored procedures. I would have to think it is because you are calling a stored procedure within a stored procedure... I imagine that setting it at the master stored procedure level would give you a performance enhancement and stop the problem associated with this error...

Brian

Brian

Hi Bmains,Melvik

I had put the set nocount on statement at master stored procedure level only. My stored procedure text is too long. If you could send me your email addresses I can email them.

Puneet

Puneet

oops my email address is [email protected]

Puneet

u can mail me from http://p2p.wrox.com/pop_profile.asp?...isplay&id=1047

Always:),
Hovik Melkomian.