SQL Server 2008 Network protocol Deep Understanding _mssql2008

SQL Server 2008 supports four protocols, Shared memory;tcp/ip;named pipes and virtual Interface Adapter (VIA). After the SQL Server Configuration Manager is opened, a node that configures the SQL Server service, SQL Server network protocol, and SQL Native client protocol is displayed. You can configure the server protocol by expanding the SQL Server 2008 Network Configuration node.

The shared memory:shared meory protocol can only be used by local connections because it is a process-shared memory space for internal communication within the server. Applications or tasks that run locally on SQL Server can take advantage of the shared Memroy protocol
The Named pipes:named pipes protocol uses interprocess communication channels for efficient server internal and LAN communications, but Named pipes requires too much overhead when connecting over a network or firewall, and it requires opening additional port 445. So in general, it is best to disable named pipes. However, there are many applications that need to use the Named pipes protocol, because they are designed around the Netbbios or LAN-granting protocol. Named pipes can easily access remote procedure calls in a single security domain, which is useful for these applications. If you need to support these applications, and SQL Server is not exposed to external traffic, the risk of enabling the Named Pipes protocol and the corresponding endpoint is minimal.
TCP/IP:TCP/IP is the primary and preferred protocol for most SQL installations.

Virtual Interface Adapter: This protocol is used in conjunction with supported hardware and network configurations. The virtual interface system, developed jointly by Compaq, now Hewlett-Packard, Intel and Microsoft, is designed to be a two-cost high-performance protocol that reduces the Pain network protocol, which runs in user-mode contexts rather than kernel-mode contexts. The Via network client is connected to the system area network.

SQL Native Client Configuration
SQL Native Client supports the same four server-side protocols, and can set the binding order of the protocols in addition to configuring the client protocols. You can use the SQL Native Client Configuration node to create aliases. By making an alias, the client's request can be directed to the server without changing the server name. Aliases can also be used to replace complex named instance names.

SQL Server Endpoint
SQL Server 2008 uses a connection object as an endpoint that allows you to listen to different ports and use different transport protocols for different services. SQL Server provides four different types of endpoints: TSQL (Default and TCP); database mirroring; Soap;service Broker.
Default TSQL Endpoint: 5 TSQL endpoints are created during Setup: TSQL default tcp,tsql default Via,tsql Named pipes,tsql Local computer, dedicated Administrator Connection (DAC, Dedicated administrator connection). The TSQL endpoint provides link services for four supported protocols, and a fifth is used to support the DAC endpoint to listen on a dedicated TCP port that is configured to support a management connection at startup. The configured ports are logged in the current SQL Server log file.

The TSQL default TCP endpoint is created during the installation of an instance of SQL Server and is automatically configured to listen on port 1433 for the default instance. Each time a named instance is started, the named instance TSQL default TCP endpoint is randomly assigned a TCP port. However, you can statically configure the port number of a named instance through SQL Server Configuration Manager. Configuring a static port simplifies client access and reduces the reliance on SQL Server Browser services for named instances of American opera.

The VIA protocol is used to support the VIA hardware device, and the VIA protocol depends on the vendor's implementation, so it is difficult to discuss the VIA endpoint without selecting a specific hardware vendor
The TSQL Named pipes endpoint is used to support Named pipes protocol connections.
TSQL Local computer endpoints allow connections using the shared memory protocol.