0

What are some simple ways to capture network failures/drops to requests sent to a sql server?

SQL Server comes with a Profiler tool, but doesnt seem to log dropped requests, instead only successful queries, which in case of failures isn't all that useful.

  • As I mentioned below : why are you certain that the problem is the network? To give the best help, we'll need a detailed description of the actual symptoms you're observing, and what troubleshooting you've done. – mfinni Dec 31 '12 at 0:22
1

I'll give some answers, then question your assumptions.

Using wireshark from both endpoints and matching traffic to see what's seen on one side but not the other is the only way to know for sure what each node sent and received. This is not usually very practical.

You can also ask query your switch for L2 and maybe L3 statistics on the port(s) in question, and maybe things like buffer problems or CPU/memory issues on the switch. If the switch is dropping packets because it's too busy or flooded, you'll want to know that.

Now, what I'd like to know is, why are you certain that the problem is the network? To give the best help, we'll need a detailed description of the actual symptoms you're observing, and what troubleshooting you've done. Many times, the problem is not the network.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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