🚀 go-pugleaf

Hate to write this but 56K won't cut running NT.  We have the same and
simply connecting to the remote server is timely.  We run 56K about 5 miles
and it too slow, but when we run our T1 across the country, it is like
having the SQL Server next door.

I am convinced that your pipe is too narrow.
-- 
Michael Blaskey
Technology Solutions Mgr - Avnet
Private email 71003.1463@compuserve.com

Sanjay <sgupta@aegonusa.com> wrote in article
<01bc282a$ff59bd60$168f7ba2@sgupta>...
> We are getting slow MS SQL server performance while updating. The network
> configuration as follows:
> 
> The client PC is NT 4.0, connected to the SQL Server via 56 k frame relay
> link using TCP/IP protocol. The protocol is routed from the client lan to
> the SQL server location by IBM 2217 routers.
> 
> The problem we are having is that response time for SQL Server records is
> about three times slower than what it is in LAN. However we have similar
> WAN links other places but they are using CISCO routers and performance
is
> not affected over the WAN link. We lloked through the SMS trace for
TCP/IP
> packets and there are TCPpackets during which we see upto 1 second
elapsed
> time even the packet size is really small.
> 
> Any ideas will be greatly appreciated.
> 
> Sanjay Gupta
> sgupta@aegonusa.com
> 
> 

Sanjay wrote:
> 

> The problem we are having is that response time for SQL Server records is
> about three times slower than what it is in LAN. However we have similar
> WAN links other places but they are using CISCO routers and performance is
> not affected over the WAN link. We lloked through the SMS trace for TCP/IP
> packets and there are TCPpackets during which we see upto 1 second elapsed
> time even the packet size is really small.

Are you using IP Sockets, or Named Pipes over Netbios over IP?  The
Netbios over IP scenario can be really messy over WAN links, as the
routers must do all sorts of nasty broadcast-spoofing.  Cisco's happen
to be very good at this stuff...Try using IP sockets, if not are you
using WINS/NBNS on the NT Servers?  We have an SQL server that we access
through a 56K link, and properly architected it can run very smoothly,
like there is no WAN at all.  

Another thing to look for is ODBC.  It tends to turn a simple 100 byte
query into pages of crap, are you using ODBC?

Dan.

Dan,

We are having the same problem using Access 95 as a front-end to SQL 6.5
SP2 running on NT 3.51 SP4.  The app has 10-12 users in the home office and
works great - the 3-4 users in the remote office experience 5-7 second
delays pulling up 500 byte records over the 56K frame relay link.  Database
connectivity is through ODBC.  I have noticed monitoring the traffic that
the ODBC layer results in dozens of lines of traffic for even the simplest
transaction.

Any ways to speed it up?????

Thanks,

Harley 

Dan Armstrong <dana@rogers.wave.ca> wrote in article
<331F1A1E.4F99@rogers.wave.ca>...
> 
> Are you using IP Sockets, or Named Pipes over Netbios over IP?  The
> Netbios over IP scenario can be really messy over WAN links, as the
> routers must do all sorts of nasty broadcast-spoofing.  Cisco's happen
> to be very good at this stuff...Try using IP sockets, if not are you
> using WINS/NBNS on the NT Servers?  We have an SQL server that we access
> through a 56K link, and properly architected it can run very smoothly,
> like there is no WAN at all.  
> 
> Another thing to look for is ODBC.  It tends to turn a simple 100 byte
> query into pages of crap, are you using ODBC?
> 
> Dan.
>