Better yet, insert a "set nocount on" for all sprocs. Most of the time you
are not even going to need to use the count of the rows affected. This,
by the way, also gives you a slight performance boost and reduced network
traffic.
|
Results 1 to 1 of 1
Thread: Re: executing long stored proc throuh ado having multile update and delete and final select statemen
|
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S. Wed Yourself to UML with the Power of Associations Microsoft to Add AJAX Capabilities to ASP.NET IBM's Cloudscape Versus MySQL | ||||||||||||||||||||||||||||||||||
![]() | |||||
|
| |||||
![]() |
Bookmarks