Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I would like to know how to isolate SQL Server bad query performance is caused by NETWORK and not the SQL Server.

Are there any specific tips and tricks in SSMS, wait types, or specific PerfMon counter permissable values as far as network is concerned? How do I baseline the network related counters and what values should I consider as good/better/poor?

share|improve this question

closed as too broad by Mark Storey-Smith, Mikael Eriksson, Max Vernon, Shawn Melton, Michael - sqlbot Dec 21 '13 at 7:36

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

Waits and Queues is a good resource for this problem. Is a methodology for investigating SQL Server performance problems. It will teach you and help you find the bottleneck, which is better than to make assumptions and try to prove your assumption. Anyway, the paper has specific advice on how to identify Network as a bottleneck. A quick check is ASYNC_NETWORK_IO wait type stats, high values indicate frequent stalls waiting for Network IO sent to the client to complete (ie. marshaling the results is slow). Read the paper for more details.

Note that well designed applications seldom are affected by network bandwith. Short of special ETL scenarions, a high bandwith requirement is an indication of bad app design, not of network problems. High Network latency also affects chatty applications more, and chattiness (many round-trips) is again a smell of bad design. Both network badnwith and latency are trivial to test and measure, again read the paper linked for methodology.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.