Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SET NOCOUNT ON (I don't mean to shout)
Message
General information
Forum:
Microsoft SQL Server
Category:
Stored procedures, Triggers, UDFs
Environment versions
SQL Server:
SQL Server 2000
Miscellaneous
Thread ID:
01075920
Message ID:
01075954
Views:
13
>>Thanks for the reply. Is it also considdered good practice to set if back off (SET NOCOUNT OFF) before exiting my SPs?
>
>You can but I don't see a reason to do that.
>
>>Just so I can understand it a little better. Lets say I have a SP with 3 UPDATE statements and SET NOCOUNT is OFF. Will the server "chat" with the client after each UPDATE statement?
>
>Yes. In QA you will see them as "nn rows affected".

Just so I am 100% clear on this <s>. If I connect to a database using OleDb or something and then execute a stored procedure the server will tell the client "nn rows affected" as many times as I have update statements in my SP (If I don't SET NOCOUNT ON)?

If that is the case it is very important to SET NOCOUNT ON in every SP (unless you are debugging <s>)

Please correct me if I made and wrong statements.

Thanks,
Einar
Semper ubi sub ubi.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform