Client network libraries in SQL Server 2005

The Client network library in SQL Server enables client applications to communicate with the SQL Server system. This article provides a brief introduction to the SQL Server 2005 Client Network library and its use, including four aspects: Shared memory, Virtual interface adapters, named pipes, and TCP/IP protocols.

In SQL Server, the client network library is critical and is a bridge between client applications and SQL Server systems to connect to and communicate. The client must use the same Client network library as the SQL Server system it needs to connect to. When a client connects over a LAN or WAN, the client network library compresses the SQL Server's tabular data stream (tabular data Stream,tds) under the appropriate network protocol. (TDs is the protocol that SQL Server uses to accept requests for network queries to put back query results to client applications). For local connections, you can use a high-performance Shared memory network library. To use the Client network library, first open SQL Server Configuration Manager, click SQL Native Client Configuration, and then select the Client Protocol node, the contents of the network protocol for the SQL Server 2005 Client network library, as shown in the following headings, appear.

Share memory (shared Memory)

Shared Memory Client network libraries can be used to connect applications running on the local server and the SQL Server engine. In SQL Server Express, this is the default configuration that communicates directly through the system's network stack using an "in-memory" pipeline, enabling you to connect to SQL Server at the fastest speed. Shared memory is the simplest protocol and there is no option to set it.

Virtual Interface Adapter (Interface Adapter,via)

The virtual interface Adapter protocol is a protocol for high-performance dedicated connections between two systems. Via provides a memory-mapped communication pattern that achieves optimal performance through the operating system network layer. For SQL Server, the VIA Client network library is typically used when you want to implement a high-performance cluster. By default, via uses port 1433, but this configuration can be reset.

Named pipes (Named pipes)

This Client network library is best suited for LAN connections. In a LAN environment, its performance is comparable to the TCP/IP client network library. By default, SQL Server receives client connections from named pipe \pipe\sql\query, but you can change the default pipe. When you use a period to specify a SQL Server system (for example, \SQLExpress), the default setting is to use named pipe connections.

TCP/IP protocol

The most widely used client protocol is TCP/IP, regardless of whether it is a local, local or WAN connection, although the TCP/IP protocol is best suited for LAN and WAN connections. In the context of wide area network, TCP/IP protocol is superior to named pipe protocol in performance. As its name shows, this client network library must be used under the TCP/IP protocol. By default, it uses port 1433, but this configuration can also be reset.