By default, SQL Server returns a friendly message to report the total number of rows affected by each query. This is a great setting for debugging your applications or modifying data directly in Query Analyzer. However, your front-end application doesn't need to know the number of affected rows -- it simply needs the data. Sending this message can introduce unnecessary network overhead.
What should you do? Use "SET NOCOUNT ON" in all your stored procedures to reduce network chatter.
Wednesday, December 26, 2007
Returning number of affected rows
Labels:
SQL Server,
SQL Tuning
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment