Re: Local named pipes better than TCP/IP?
From: PerFry (PerFry_at_discussions.microsoft.com)
Date: 11/22/04
- Next message: Steve Thompson: "Re: Connecting from outside world"
- Previous message: Carl Olsson: "Cannot connect in mixed mode after installing SQL2K on client"
- In reply to: Rand Boyd [MSFT]: "Re: Local named pipes better than TCP/IP?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Nov 2004 03:53:03 -0800
I'd like to stress that we're having the client and server on the same
machine, so I'm referring to _local_ named pipes. Books Online states that
"Local named pipes runs in kernel mode and is extremely fast" (
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbcsql/od_odbc_g_5l9r.asp ).
"Rand Boyd [MSFT]" wrote:
> With SQL Server 2000 the default for local connections (connections made on
> the server itself) is shared memory. Steve is correct that named pipes is
> for the most part a legacy connection method. I would just use the default
> of shared memory for local connections and TCP/IP for remote connections.
>
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
>
- Next message: Steve Thompson: "Re: Connecting from outside world"
- Previous message: Carl Olsson: "Cannot connect in mixed mode after installing SQL2K on client"
- In reply to: Rand Boyd [MSFT]: "Re: Local named pipes better than TCP/IP?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
