SQL Server Configuration Manager
Applies to: SQL Server
SQL Server Configuration Manager is a tool to manage the services associated with SQL Server, to configure the network protocols used by SQL Server, and to manage the network connectivity configuration from SQL Server client computers. Beginning with SQL Server 2022 (16.x), you can use 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 Microsoft Management Console snap-in that is available from the Start menu, or can be added to any other Microsoft Management Console display. Microsoft Management Console (mmc.exe) uses the SQLServerManager<version>.msc file (such as SQLServerManager13.msc for SQL Server 2016 (13.x)) to open Configuration Manager. You'll need the corresponding SQL Server Configuration Manager version to manage that particular version of SQL Server. Here are the paths to the last five versions when Windows is installed on the C drive.
|SQL Server 2022||C:\Windows\SysWOW64\SQLServerManager16.msc|
|SQL Server 2019||C:\Windows\SysWOW64\SQLServerManager15.msc|
|SQL Server 2017||C:\Windows\SysWOW64\SQLServerManager14.msc|
|SQL Server 2016||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, SQL Server Configuration Manager does not appear as an application in newer versions of Windows.
Windows 10 or 11:
To open SQL Server Configuration Manager, navigate to the file location listed above for your version. Select SQLServerManager16.msc to open the Configuration Manager. You can also right-click SQLServerManager16.msc to pin the Configuration Manager to the Start Page or Task Bar.
To open SQL Server Configuration Manager, in the Search charm, under Apps, type SQLServerManager<version>.msc such as SQLServerManager13.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 SQL Server tools and to provide 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 Connect to Another Computer (SQL Server Configuration Manager).
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 Database Engine using startup parameters. For more information, see Configure Server Startup Options (SQL Server Configuration Manager).
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.
Changing the accounts used by the services
Manage the SQL Server services using SQL Server Configuration Manager.
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, SQL Server Configuration Manager performs additional configuration 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 do not change associated settings. If the service cannot access the SQL Server portion of the registry the service may not start properly.
As an extra benefit, passwords changed using SQL Server Configuration Manager, SMO, or WMI take effect immediately without restarting the service.
Manage server & client network protocols
SQL Server Configuration Manager allows you to configure server and 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 SQL Server listens on a particular network protocol, port, or 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.
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 ISA Server documentation.