had expected TCP connections to run better (or at very least equal)
to their
Named Pipes counterparts, but it doesn't seem to be going that way for us
right now...
Any other suggestions? :)
-Jah
- Original Message -
From: "Andrian Pervazov" <[EMAIL PROTECTED]>
To:
Hello! :)
I've run into a problem where connecting to our MSSQL Server from our
webserver using a TCP/IP connection is a -whole- lot slower than
connecting to the same server using a Named Pipes connection (we're
talking 10 to 20 times slower).
We are running SQL server on a non-standard port
Hello! :)
I've run into a problem where connecting to our MSSQL Server from our
webserver using a TCP/IP connection is a -whole- lot slower than
connecting to the same server using a Named Pipes connection (we're
talking 10 to 20 times slower).
We are running SQL server on a non-standard port
