Tools to test the speed

[Agnes]

My client put the SQL server in data center. Their branches (located in
different area) run vb.net application via VIA VFP . Now, they complaint
that there is Timeout occurs.
When I test the system locally, it run very fast and fine. I think it is the
internet problem . However, I just a SA but not network admin. any tools can
I put in the vb.net application and let them test the speed ??

 

[Guest]

When I test the system locally, it run very fast and fine. I think it
is the internet problem . However, I just a SA but not network admin.
any tools can I put in the vb.net application and let them test the
speed ??

If it is a network issue, you should use network diagnostic tools.

PING/TraceRoute which are included with Windows often provides enough data.
Otherwise you can use something like Wireshark (Ethereal) to capture
packets to see what's going on the wire.

Lastly you can use a traffic generator to see how much data you can send
across the wire, that shoul give you a good idea of the bandwidth (and
reliablity) of the link. Of course you should run such a test with the
knowledge of the network admin ... and the users of the network

 

[E C H (He of too much code)]

My client put the SQL server in data center. Their branches (located in
different area) run vb.net application via VIA VFP . Now, they complaint
that there is Timeout occurs.
When I test the system locally, it run very fast and fine. I think it is the
internet problem . However, I just a SA but not network admin. any tools can
I put in the vb.net application and let them test the speed ??

If you create test data in the SQL server (or something that you know will never change),
you could locally time pulling all the data/running a specific query (even one that you
know will return nothing), say 100 or more times (average that). Use this time as a
baseline. Then allow the remote users to run the same query, then you could return a +/-
of the time it takes them to perform the same query. For instance they could return -140,
or 140 seconds longer than your "local" query. You will probably want to increase the
timeout.

 

[Freddy Coal]

You can make a timer inside your code in milliseconds, for take the time
that take the code.

For example:

Dim firstResult, secondResult As Double
Dim swatch As New Stopwatch()
swatch.Start()

<<<< YOUR CODE HERE >>>>

firstResult = swatch.ElapsedMilliseconds

<<<< YOUR CODE HERE >>>>

secondResult = swatch.ElapsedMilliseconds
MsgBox(firstResult & intro & secondResult)
swatch.Stop()

My best regards.

Freddy Coal