Edit

Share via

SQL Server Configuration Manager

  • Article

Applies to: SQL Server - Windows only

SQL Server Configuration Manager is a tool to manage the services associated with SQL Server, configure the network protocols used by SQL Server, and manage the network connectivity configuration from SQL Server client computers. In SQL Server 2022 (16.x) and later versions, you can also use SQL Server Configuration Manager to manage the Azure extension for SQL Server.

SQL Server Configuration Manager is installed automatically with your SQL Server installation. It's a Microsoft Management Console (MMC) snap-in that can be accessed from the Start menu or added to any other MMC display. The MMC uses the SQLServerManager<version>.msc file (for example, SQLServerManager16.msc for SQL Server 2022) to open SQL Server Configuration Manager.

Version Path
SQL Server 2022 (16.x) C:\Windows\SysWOW64\SQLServerManager16.msc
SQL Server 2019 (15.x) C:\Windows\SysWOW64\SQLServerManager15.msc
SQL Server 2017 (14.x) C:\Windows\SysWOW64\SQLServerManager14.msc
SQL Server 2016 (13.x) C:\Windows\SysWOW64\SQLServerManager13.msc
SQL Server 2014 (12.x) C:\Windows\SysWOW64\SQLServerManager12.msc
SQL Server 2012 (11.x) C:\Windows\SysWOW64\SQLServerManager11.msc

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

Access SQL Server Configuration Manager

  • Windows 10 and Windows 11: To open SQL Server Configuration Manager, type SQLServerManager16.msc (for SQL Server 2022) in the Start Page. For other versions, replace 16 with the appropriate number. You can pin SQL Server Configuration Manager to the Start Page or Task Bar by right-clicking SQLServerManager16.msc and selecting "Open file location." Then, right-click the file and select "Pin to Start" or "Pin to Taskbar".
  • Windows 8: In the Search charm, under Apps, type SQLServerManager<version>.msc (for example, SQLServerManager16.msc) and 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 to interface with API calls and manages the registry operations requested by the SQL Server 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

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

Use SQL Server Configuration Manager to start the Database Engine using startup parameters. For more information, see SQL Server Configuration Manager: Configure server startup options.

Beginning with SQL Server 2022 (16.x), you can use SQL Server Configuration Manager to start, pause, resume, or stop Azure extension for SQL Server.

Change accounts used by services

Manage the SQL Server services using SQL Server Configuration Manager.

Important

Always use SQL Server tools such as SQL Server Configuration Manager to change the account used by the SQL Server or SQL Server Agent services or to change the password for the account. In addition to changing the account name, the SQL Server Configuration Manager performs additional configurations, such as setting permissions in the Windows Registry so that the new account can read the SQL Server 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 SQL Server 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 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 SQL Server 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, include forcing protocol encryption, viewing alias properties, and enabling/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 don't 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

SQL Server supports Shared Memory, TCP/IP, and Named Pipes protocols. For information about choosing network protocols, see Configure Client Protocols. SQL Server 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 SQL Server. 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