TCP/IP and Pipes for and ODBC Connection [modified]
-
Hi, I have a problem with and app that is connected to an SQL 2000 database The user got a new server dual CPU 3.2 GHz Pentium 4 with 2G memory and the app is slower compare with the old machine a dual CPU 755 MHz Pentium 3 with 512 memory. If you use the TCP/IP connection in ODBC driver, the new machine is very slow. If you use Name Pipe in ODBC, both machine a doing well. The old machine it is working well with both TCP/IP and Pipes. Does anybody have any idea why it is such a big difference between TCP/IP and pipes for the new machine? The different is from 1 minute to 10 minutes for an operation. Any thoughts are welcome Thanks, Florian -- modified at 15:01 Friday 16th June, 2006
-
Hi, I have a problem with and app that is connected to an SQL 2000 database The user got a new server dual CPU 3.2 GHz Pentium 4 with 2G memory and the app is slower compare with the old machine a dual CPU 755 MHz Pentium 3 with 512 memory. If you use the TCP/IP connection in ODBC driver, the new machine is very slow. If you use Name Pipe in ODBC, both machine a doing well. The old machine it is working well with both TCP/IP and Pipes. Does anybody have any idea why it is such a big difference between TCP/IP and pipes for the new machine? The different is from 1 minute to 10 minutes for an operation. Any thoughts are welcome Thanks, Florian -- modified at 15:01 Friday 16th June, 2006
my guess is Named-Pipes and ODBC are better at buffering, while TCP/IP works to a point then TCP/IP becomes saturated and network performance decreases. (but there's a lot of variables here) 'g'