Skip to content

Latest commit

 

History

History
95 lines (67 loc) · 10.2 KB

sql-server-configuration-manager.md

File metadata and controls

95 lines (67 loc) · 10.2 KB
title description author ms.author ms.reviewer ms.date ms.service ms.topic helpviewer_keywords
SQL Server Configuration Manager
Utilizing the SQL Server Configuration Manager client
markingmyname
maghan
randolphwest, vanto
09/11/2024
sql
conceptual
protocols [SQL Server], managing
network protocols [SQL Server], managing
Client Network Utility
accounts [SQL Server]
SQL Server Configuration Manager
Server Network Utility
accounts [SQL Server], services
services [SQL Server], managing
tools [SQL Server], SQL Server Configuration Manager
configuration manager [SQL Server]

SQL Server Configuration Manager

[!INCLUDE sqlserver]

SQL Server Configuration Manager is a tool to manage the services associated with [!INCLUDE ssNoVersion], to configure the network protocols used by [!INCLUDE ssNoVersion], and to manage the network connectivity configuration from [!INCLUDE ssNoVersion] client computers. In [!INCLUDE sssql22-md] and later versions, you can use SQL Server Configuration Manager to manage the Azure extension for SQL Server.

SQL Server Configuration Manager is installed with your SQL Server installation. SQL Server Configuration Manager is a [!INCLUDE msCoName] Management Console snap-in that is available from the Start menu, or can be added to any other [!INCLUDE msCoName] Management Console display. [!INCLUDE msCoName] Management Console (mmc.exe) uses the SQLServerManager<version>.msc file (such as SQLServerManager13.msc for [!INCLUDE sssql15-md]) to open SQL Server Configuration Manager. You need the corresponding SQL Server Configuration Manager version to manage that particular version of [!INCLUDE ssNoVersion]. Here are the paths to the last five versions when Windows is installed on the C drive.

Version Path
[!INCLUDE sssql22-md] C:\Windows\SysWOW64\SQLServerManager16.msc
[!INCLUDE sssql19-md] C:\Windows\SysWOW64\SQLServerManager15.msc
[!INCLUDE sssql17-md] C:\Windows\SysWOW64\SQLServerManager14.msc
[!INCLUDE sssql16-md] C:\Windows\SysWOW64\SQLServerManager13.msc
[!INCLUDE sssql14-md] C:\Windows\SysWOW64\SQLServerManager12.msc
[!INCLUDE sssql11-md] C:\Windows\SysWOW64\SQLServerManager11.msc

Because SQL Server Configuration Manager is a snap-in for the [!INCLUDE msconame-md] Management Console program and not a stand-alone program, SQL Server Configuration Manager doesn't appear as an application in newer versions of Windows.

Operating system Details
Windows 10 and Windows 11 To open SQL Server Configuration Manager, on the Start Page, type SQLServerManager16.msc (for [!INCLUDE sssql22-md]). For other versions of [!INCLUDE ssNoVersion], replace 16 with the appropriate number. Selecting SQLServerManager16.msc opens the SQL Server Configuration Manager. To pin the SQL Server Configuration Manager to the Start Page or Task Bar, right-click SQLServerManager16.msc, and then select Open file location. In the Windows File Explorer, right-click SQLServerManager16.msc, and then select Pin to Start or Pin to taskbar.
Windows 8 To open SQL Server Configuration Manager, in the Search charm, under Apps, type SQLServerManager<version>.msc, such as SQLServerManager16.msc, and then press Enter.

SQL Server Configuration Manager and SQL Server Management Studio use Window Management Instrumentation (WMI) to view and change some server settings. WMI provides a unified way for interfacing with the API calls that manage the registry operations requested by the [!INCLUDE ssNoVersion] tools. WMI also provides enhanced control and manipulation over the selected SQL services of the SQL Server Configuration Manager snap-in component. For information about configuring permissions related to WMI, see Configure WMI to Show Server Status in SQL Server Tools.

To start, stop, pause, resume, or configure services on another computer by using SQL Server Configuration Manager, see SQL Server Configuration Manager: Connect to another computer.

Manage services

Use SQL Server Configuration Manager to start, pause, resume, or stop the services, to view service properties, or to change service properties.

Use SQL Server Configuration Manager to start the [!INCLUDE ssDE] using startup parameters. For more information, see SQL Server Configuration Manager: Configure server startup options.

Beginning with [!INCLUDE sssql22-md], you can use SQL Server Configuration Manager to start, pause, resume, or stop Azure extension for SQL Server.

Change the accounts used by the services

Manage the [!INCLUDE ssNoVersion] services using SQL Server Configuration Manager.

Important

Always use [!INCLUDE ssNoVersion] tools such as SQL Server Configuration Manager to change the account used by the [!INCLUDE ssNoVersion] or [!INCLUDE ssNoVersion] Agent services, or to change the password for the account. In addition to changing the account name, SQL Server Configuration Manager performs additional configuration such as setting permissions in the Windows Registry so that the new account can read the [!INCLUDE ssNoVersion] settings. Other tools such as the Windows Services Control Manager can change the account name but don't change associated settings. If the service can't access the [!INCLUDE ssNoVersion] portion of the registry the service might not start properly.

As an extra benefit, passwords changed using SQL Server Configuration Manager, SQL Server Management Objects (SMO), or WMI take effect immediately without restarting the service.

Manage server and client network protocols

SQL Server Configuration Manager allows you to configure server or client network protocols and connectivity options. After the correct protocols are enabled, you usually don't need to change the server network connections. However, you can use SQL Server Configuration Manager if you need to reconfigure the server connections so [!INCLUDE ssNoVersion] listens on a particular network protocol, port, or named pipe. For more information about enabling protocols, see Enable or disable a server network protocol. For information about enabling access to protocols through a firewall, see Configure the Windows Firewall to allow SQL Server access.

SQL Server Configuration Manager allows you to manage server and client network protocols, including the ability to force protocol encryption, view alias properties, or enable/disable a protocol.

SQL Server Configuration Manager allows you to create or remove an alias, change the order in which protocols are used, or view properties for a server alias, including:

  • Server Alias - The server alias used for the computer to which the client is connecting.
  • Protocol - The network protocol used for the configuration entry.
  • Connection Parameters - The parameters associated with the connection address for the network protocol configuration.

Note

SQL Server 2022 and later versions do not support creating aliases using SQL Server Configuration Manager. To create an alias for SQL Server 2022 and later versions, use the SQL Server Client Network Utility tool.

The SQL Server Configuration Manager also allows you to view information about failover cluster instances, though Cluster Administrator should be used for some actions such as starting and stopping the services.

Available network protocols

[!INCLUDE ssNoVersion] supports Shared Memory, TCP/IP, and Named Pipes protocols. For information about choosing network protocols, see Configure Client Protocols. [!INCLUDE ssNoVersion] doesn't support VIA, Banyan VINES Sequenced Packet Protocol (SPP), Multiprotocol, AppleTalk, or NWLink IPX/SPX network protocols. Clients previously connecting with these protocols must select a different protocol to connect to [!INCLUDE ssNoVersion]. You can't use SQL Server Configuration Manager to configure the WinSock proxy. To configure the WinSock proxy, see your Internet Security and Authentication Server (ISA) documentation.

Related content