Subject | Re: All about different connection strings? |
---|---|
Author | Aage Johansen |
Post date | 2002-11-03T20:41:29Z |
Helen wrote:
<<
If you are noticing the slowdown with a localhost connection, as compared
with a local connection, the cause is more likely to do with competition
from NetBEUI and/or IPX/SPX on the server's protocol stack than with local
loopback. Does your DB server need those other protocols at all? If you
need either of them, what is the effect if you remove and then re-add them,
to force TCP/IP to the top of the stack?
imperceptibly so?
I don't think there are any traces of IPX/SPX on our LAN (now using TCP/IP
with Netware/6).
I might be able to remove NetBEUI. I did this a long time ago on a WinNT4
server, which gave me an uncomfortable feeling before things settled down -
maybe booting once or twice was necsssary. I don't really enjoy fiddling
with something that works...
I'll check out about TCP/IP being on top.
Regards,
Aage J.
<<
If you are noticing the slowdown with a localhost connection, as compared
with a local connection, the cause is more likely to do with competition
from NetBEUI and/or IPX/SPX on the server's protocol stack than with local
loopback. Does your DB server need those other protocols at all? If you
need either of them, what is the effect if you remove and then re-add them,
to force TCP/IP to the top of the stack?
>>Shouldn't a local connection be faster than TCP/IP? Maybe just
imperceptibly so?
I don't think there are any traces of IPX/SPX on our LAN (now using TCP/IP
with Netware/6).
I might be able to remove NetBEUI. I did this a long time ago on a WinNT4
server, which gave me an uncomfortable feeling before things settled down -
maybe booting once or twice was necsssary. I don't really enjoy fiddling
with something that works...
I'll check out about TCP/IP being on top.
Regards,
Aage J.