|
Home > Archive > MS SQL Server > March 2006 > Ping responses from a SQL Server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Ping responses from a SQL Server
|
|
| Hassan 2006-03-05, 8:24 pm |
| I was pinging a SQL Server and noticed that the replies are not always < 1ms
.. Why would that be ? If the NIC speed and duplex settings are set right,
could it also be high as such if there is more data being moved back and
forth and if so, do we need to upgrade the port ? Right now we are sitting
on a 100 Mbps full
Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
Reply from 12.156.2.56: bytes=32 time=15ms TTL=127
Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
Reply from 12.156.2.56: bytes=32 time<7ms TTL=127
Reply from 12.156.2.56: bytes=32 time=11ms TTL=127
Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
Reply from 12.156.2.56: bytes=32 time<9ms TTL=127
Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
I am not a network guy, but I feel concerned to see those variations. Let me
know
Thanks
| |
| Eric Proegler 2006-03-05, 8:24 pm |
| Hello Hassan,
You can frequently get variable ping returns due to other load on the
network/network hardware, quality of the copper, etc. If you set the ping to
run for a while, you should see variable results over time, especially on a
production network with lots of traffic flying around.
How many hops are you making? tracert 12.156.2.56 from the command prompt
will answer that. I suspect it is only one, but it's worth checking out.
15ms is not optimal, but it is not terrible, either. If you have an
especially "chatty" application (many round trips to the database), you might
see an impact, but query processing won't be any different, of course.
HTH,
Eric
"Hassan" wrote:
> I was pinging a SQL Server and noticed that the replies are not always < 1ms
> .. Why would that be ? If the NIC speed and duplex settings are set right,
> could it also be high as such if there is more data being moved back and
> forth and if so, do we need to upgrade the port ? Right now we are sitting
> on a 100 Mbps full
>
> Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
> Reply from 12.156.2.56: bytes=32 time=15ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<7ms TTL=127
> Reply from 12.156.2.56: bytes=32 time=11ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<9ms TTL=127
> Reply from 12.156.2.56: bytes=32 time<1ms TTL=127
>
> I am not a network guy, but I feel concerned to see those variations. Let me
> know
>
> Thanks
>
>
>
|
|
|
|
|