Well one way or the other the latency of the link does seem to be the most
important factor in the problem I'm seeing.
I have three ways to get at the data:
1) log into the remote server using RDP and run the queries locally. even the
most complex ones complete in under a second
2) use JDBC
Em 27/4/2012 15:11, Maury Markowitz escreveu:
Well one way or the other the latency of the link does seem to be the most
important factor in the problem I'm seeing.
I have three ways to get at the data:
1) log into the remote server using RDP and run the queries locally. even the
most
The database in question is only 50 MB on disk and the tables I'm talking to
are generally only a few hundreds rows and maybe 20
columns nothing but char, int and float. It's all very small and light!
Running on the server, over the VPN and using RDP, the simple queries I run
complete almost
Moreover, I can see that during the delays, the *outbound* link from the
client is clicking over about 1 kbps for the entire period. It *appears* that
the client is dribbling out information that the server is waiting on,
although I can't imagine what it is.
The client does fetch the
