SQL Server over Point-to-Point T1

I'm running SQL Server 2005 on a Server 2003 machine serving both our home network as well as a remote site through a point-to-point T1. While file transfer speeds are up to par, the remote site's interaction with SQL Server (Point of sale system) is very slow. After testing I am certain that it has nothing to do with the actual physical machine in place neither is it an issue with the program itself since speeds are as they are supposed to be over the home network lan. It seems that there might be a packet size issue or something of the sort. Has anyone dealt with this before or have any thoughts

Thanks,
Peter

Answer this question

SQL Server over Point-to-Point T1

James Holmes 747
It's about 1/10 of the bandwith of a straight file transfer. The connection to the server is as an ODBC data source on the remote machines. No encryption. I understand the difference in the transmision of data but the speed should not be 1/10 slower over a full T1 (1.56 Mb/s)
Sneha Desai
If your app open&close connection for every sql query, you get connection penalties which can be large because there are several handshakes to establish a secure SQL connection before a query is issued against the server.
If you can provider the following data, I can see if it make any sense.

"ping <servername>" to get the round trip latency of your T1 line.

The code that you issue queries.
Billlong
5ms and they are all SELECT queries
zoomer
How bad is the speed What is your configuration and connection string Do you keep connection open Do you have encryption on

It is not an apple to apple comarison between file transfer and SQL query. File transfer is like "pipelined" in that it sends multiple packet out without acknowlegement from its peer if there is enought data to send and receiver has enought buffer window announced. SQL protocol is very "chatty" in that it normally send a request, which can be small, and wait for a response. Such stop and go effect of SQL protocol magnify on the large latency link as slow speed. Also, if your app open&close connection for every sql query, you get connection penalties which can be large because there are several handshakes to establish a secure SQL connection before the query is issued against the server.

If you can provider the following data, I can see if it make any sense.

"ping <servername>" to get the round trip latency of your T1 line.

The code that you issue queries.
J-J-J
Is Point-to-Point T1 the same as Frame relay or a regular T1 Line
Wilhelm Knutsen
How big is your result set.
SQL Server over Point-to-Point T1

Answer this question