Page 122 - DCAP508_DATABASE_ADMINISTRATION

Database Administration

Notes apparent with slower networks, such as across wide area networks (WANs) or dial-up networks.
This is because of the different ways the interprocess communication (IPC) mechanisms
communicate between peers.
For named pipes, network communications are typically more interactive. A peer does not send
data until another peer asks for it using a read command. A network read typically involves a
series of peek named pipes messages before it starts to read the data. These can be very costly in
a slow network and cause excessive network traffic, which in turn affects other network clients.

It is also important to clarify if you are talking about local pipes or network pipes. If the server
application is running locally on the computer that is running an instance of SQL Server, the
local Named Pipes protocol is an option. Local named pipes runs in kernel mode and is very fast.
For TCP/IP Sockets, data transmissions are more streamlined and have less overhead. Data
transmissions can also take advantage of TCP/IP Sockets performance enhancement mechanisms
such as windowing, delayed acknowledgements, and so on. This can be very helpful in a slow
network. Depending on the type of applications, such performance differences can be significant.

TCP/IP Sockets also support a backlog queue. This can provide a limited smoothing effect compared
to named pipes that could lead to pipe-busy errors when you are trying to connect to SQL Server.
Generally, TCP/IP is preferred in a slow LAN, WAN, or dial-up network, whereas named pipes
can be a better choice when network speed is not the issue, as it offers more functionality, ease
of use, and configuration options.

Did u know? By default, the only network protocols enabled ob most of the edition of SQL
server are TCP/IP and Shared memory.

Self Assessment

Fill in the blanks:

1. …………………… is the simplest protocol to use and has no configurable settings.
2. …………………… includes standards for routing network traffic and offers advanced
security features.

3. Named Pipes is a protocol developed for ……………………
4. VIA stands for …………………… protocol
5. By default, the only network protocols enabled on most of the edition of SQL server are
……………………
6. Clients that use MDAC 2.8 or earlier cannot use …………………… protocol.

8.2 Enabling and Configuring Protocols

SQL Server Configuration Manager incorporates the functions of Client Network Utility from
earlier versions of SQL Server and provides client-configuration functionality for any version of
SQL Server compatible with SQL Server.
To launch SQL Server Configuration Manager, click Start, point to Program Files, point to
Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration
Manager. To access the client configuration section, in the console pane click SQL Server Native
Client Configuration.

116 LOVELY PROFESSIONAL UNIVERSITY