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.

Ping screenshot

Improve this question
6
  • Is it on the same local network?
    – DavidPostill ♦
    Sep 23, 2014 at 21:55
  • Don't beleive that IT guy...
    – Jan
    Sep 23, 2014 at 21:55
  • 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
    Sep 23, 2014 at 21:55
  • 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
    Sep 24, 2014 at 1:33
  • 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
    Sep 24, 2014 at 9:23

1 Answer 1

Reset to default
0

You can destroy MSSQL, the Windows OS, and Disk system; and the machine should never become unreachable. Slow as heck, but never a dropped ICMP packet. At least in my 20 years of demolishing MSSQL (usually by a really bad report)

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .