Re: Local named pipes better than TCP/IP?
From: Rand Boyd [MSFT] (rboyd_at_onlinemicrosoft.com)
Date: 11/18/04
- Next message: Z: "Re: SQL Server and SP2"
- Previous message: Sue Hoegemeier: "Re: Error in SQL Server Database"
- In reply to: Steve Thompson: "Re: Local named pipes better than TCP/IP?"
- Next in thread: PerFry: "Re: Local named pipes better than TCP/IP?"
- Reply: PerFry: "Re: Local named pipes better than TCP/IP?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 18 Nov 2004 22:03:56 GMT
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: Z: "Re: SQL Server and SP2"
- Previous message: Sue Hoegemeier: "Re: Error in SQL Server Database"
- In reply to: Steve Thompson: "Re: Local named pipes better than TCP/IP?"
- Next in thread: PerFry: "Re: Local named pipes better than TCP/IP?"
- Reply: PerFry: "Re: Local named pipes better than TCP/IP?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|