Network protocols used by SQL Server 2005

Before the client computer connects to the database engine, the server must listen on the enabled network library and require the server network protocol to be enabled. The following settings can be made using SQL Server Configuration Manager.

Enable the server protocol on which the SQL Server instance listens.

Disables server protocols that are no longer needed.

Specify or change each database engine, the IP address that will listen, TCP/IP ports, and named Pipes.

Enable Secure Sockets Layer encryption for all enabled server protocols.

To connect to the SQL Server 2005 database engine, you must enable network protocols. SQL Server 2005 databases can serve requests at once through a variety of protocols. The client connects to SQL Server with a single protocol. If the client program does not know which protocol SQL Server is listening on, you can configure the client to try multiple protocols sequentially. The following are the network protocols used by SQL Server 2005.

1.Shared Memory Protocol

Shared memory is the simplest protocol available, with no configurable settings. Because clients using the shared memory protocol can only connect to an instance of SQL Server running on the same computer, it is useless for most database activities. If you suspect that other protocol configurations are incorrect, you can use the Shared memory protocol for troubleshooting.

2.TCP/IP protocol

TCP/IP is a common protocol widely used on the Internet. It communicates with computers with different hardware structures and operating systems in the Internet. It includes standards for routing network traffic and provides advanced security features. The TCP/IP protocol is the most commonly used protocol in business today.

3.Named Pipes protocol

Named Pipes is a protocol developed for the LAN. Its mode of operation is that part of memory is used by a process to pass information to another process. Therefore, the output of one process is the input of another process. The second process can be local or remote.

4.VIA protocol

The virtual interface Adapter (VIA) protocol is used in conjunction with the VIA hardware. Consult your hardware vendor for information about using via.

5.Named Pipes and TCP/IP socket protocol

In a fast LAN environment, the performance of Transmission Control Protocol or Internet Protocol (TCP/IP) socket clients and named Pipes clients is similar. However, the slower the network speed, the more pronounced the performance differences between TCP/IP Sockets clients and named Pipes clients, because the mechanism of interprocess communication (IPC) communicates differently between peers.

Note: This protocol must be enabled on both the client and the server before it works properly. The server can listen for requests for all enabled protocols at the same time. The client computer can select a protocol, or try these protocols in the order listed in SQL Server Configuration Manager.