0
The issue is that our SQL machine will just disappear from the network with request timed out when I attempt to ping it.
I have to deal with an "IT Guy" who is telling me that it is because Microsoft SQL 2012 running on Server 2012 R2 is too "busy" and that's why it's unreachable.
The pings have a reply time of <5ms then unreachable several times then <5ms. If the machine were busy, I'd expect it to have long ping reply times...not just unreachable and then great pings.
Also, the machine is 16 core with 64GB of memory.
Alex K
Posted 2014-09-23T21:53:21.860
Reputation: 204
Is it on the same local network? – DavidPostill – 2014-09-23T21:55:36.967
Don't beleive that IT guy... – Jan – 2014-09-23T21:55:41.077
Same local network. They're both VMs. The guy denies everything is an issue, but I don't have enough access to the machines or visibility to prove him wrong most of the time. Is there any "hard evidence" that I can present that would prove him wrong? – Alex K – 2014-09-23T21:55:57.287
If they are VM's can you verify that "IT guy" has not limited the amount of CPU or memory to an insufficient amount. – cybernard – 2014-09-24T01:33:10.923
have you tried pinging it from a different device? I know our SQL server goes a bit silly when it maxes out on RAM. – YetiFiasco – 2014-09-24T09:23:16.420
Long ping reply times wouldn't be because the machine was busy as that does not affect ping. A machine is much more likely to ignore or drop packets if it has no resources to deal with them. – YetiFiasco – 2014-09-24T09:24:38.497