Geeks With Blogs

The Wrecking Bawl Destructuring query language, one keyword at a time.

I'm curious what percentage of developers use SET NOCOUNT ON in their stored procedures on a regular basis, particularly when they don't know exactly what code (particularly ASP.Net code) will be used to call the procedure.  My general practice has been to not use it just because I don't know when my fellow coders will use SQLDataReader.RecordsAffected or SQLDataAdapter.Update() (thanks again Jon), but I often wonder if I should just always include it and then just change it when I get a complaint.  That could be problematic though, since the coder calling the proc could spend hours trying to get things to work before he or she realizes that the proc purposely isn't sending the count.

Thoughts anyone?

Posted on Tuesday, December 12, 2006 7:57 PM all tech stuff , SQL Server , general .Net stuff | Back to top

Comments on this post: SET NOCOUNT ON with ASP.Net?

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Alex Bransky | Powered by: