03.SQL Server Configuration Manager Basic Usage

SQL Server Configuration Manager (for short, Configuration Manager) contains the SQL Server service, SQL Server network configuration, and SQL Native client configuration 3 Tools for database administrators to do server start stop and monitoring, server-side supported network protocol configuration, Users to access network-related settings such as SQL Server.

Description

Network configuration

SQL Server can use a variety of protocols, including shared Memory, Named Pipes, TCP/IP, and via. All of these protocols have separate server and client configurations. With SQL Server network configuration, you can set up network configurations independently for each server instance.

The protocols listed on the right side of the window function as follows.

1. Shared Memory protocol: the shared memory protocol is only used for local connections, and if the protocol is enabled, any local client can use this protocol to connect to the server. If you do not want local customers to use the shared Shared memory protocol, you can disable it.
2. Name Pipes protocol: The name Pipes protocol is primarily used for local connections and remote connections to previous versions of Windows 2008 operating systems.
3. TCP/IP protocol: The TCP/IP protocol is the preferred protocol for connecting to SQL Server either locally or remotely. When using the TCP/IP protocol, SQL Server listens on the specified TCP port and IP address for requests that have responded to it.
4. VIA protocol: If two or more instances of SQL Server are installed on the same computer, the VIA connection may be ambiguous. When the VIA protocol is enabled, it attempts to use TCP/IP settings and listens on port 0:1433. For via drivers that do not allow the configuration of ports, two instances of SQL Server will listen to the same port.

03.SQL Server Configuration Manager Basic Usage