Page 123 - DCAP508_DATABASE_ADMINISTRATION

Unit 8: Configuring SQL Server Network Communication

Use SQL Server Configuration Manager to: Notes
Change the default protocol, used by clients when attempting to connect to a server.
Change the order in which all enabled protocols are attempted, when connecting to a server.

Create client connections to specified servers and save them as configuration entries.
Configuration entries consist of a server alias, a client protocol, and any relevant connection
parameters, such as a pipe name, or port number.

Display information about the SQL Server client protocols currently installed on the system.

Notes SQL Server Configuration Manager creates registry entries for the server alias
configurations and default client network library. However, the application does not
install either the SQL Server client network libraries or the network protocols. The SQL
Server client network libraries are installed during SQL Server Setup; the network protocols
are installed as part of Microsoft Windows Setup (or through Networks in Control Panel).
A particular network protocol may not be available as part of Windows Setup. For more
information about installing these network protocols, see the vendor documentation.

Task List the steps to launch SQL Server Configuration Manager

8.3 Native Client Configuration

SQL Server Native Client is the network library that client computers use to connect to SQL
Server, starting with Microsoft SQL Server.
The settings configured in SQL Server Native Client Configuration, are used on the computer
running the client program. When configured on the computer running SQL Server, they affect
only those client programs running on the server.

These settings do not affect clients connecting to previous versions of SQL Server, unless they
are using the client tools starting with SQL Server, such as SQL Server Management Studio

8.3.1 Client Protocols Properties (Order Tab)

Use the Orderpage on the Client Protocols Properties dialog box to view and enable the client
protocols.
Click a protocol, and then click Enable or Disable to move the selected protocol to the Disabled
Protocols or Enabled Protocols list.
Protocols are tried in the order listed, attempting to connect using the top protocol first, and
then the second listed protocol, etc. Move protocols up or down the Enabled Protocols list, by
clicking the up arrow and down arrow buttons. When connecting to Microsoft SQL Server from
a client on that computer, the Shared Memory protocol will always be tried first, if enabled.

Notes These settings are not used by Microsoft .NET SqlClient. The protocol order for
.NET SqlClient is first TCP, and then named pipes, which cannot be changed.

LOVELY PROFESSIONAL UNIVERSITY 117