Skip to content

Latest commit

 

History

History
93 lines (68 loc) · 10.7 KB

File metadata and controls

93 lines (68 loc) · 10.7 KB
title SQL Server Configuration Manager | Microsoft Docs
description Utilizing the SQL Server Configuration Manager client
ms.custom
ms.date 12/31/2019
ms.prod sql
ms.prod_service database-engine
ms.reviewer vanto
ms.technology
ms.topic conceptual
helpviewer_keywords
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]
ms.assetid e6beaea4-164c-4078-95ae-b9e28b0aefe8
author rothja
ms.author jroth

SQL Server Configuration Manager

[!INCLUDEsqlserver]

[!INCLUDEssNoVersion] Configuration Manager is a tool to manage the services associated with [!INCLUDEssNoVersion], to configure the network protocols used by [!INCLUDEssNoVersion], and to manage the network connectivity configuration from [!INCLUDEssNoVersion] client computers. [!INCLUDEssNoVersion] Configuration Manager is installed with your SQL Server installation. [!INCLUDEssNoVersion] Configuration Manager is a [!INCLUDEmsCoName] Management Console snap-in that is available from the Start menu, or can be added to any other [!INCLUDEmsCoName] Management Console display. [!INCLUDEmsCoName] Management Console (mmc.exe) uses the SQLServerManager<version>.msc file (such as SQLServerManager13.msc for [!INCLUDEsssql15-md]) to open Configuration Manager. You will need the corresponding [!INCLUDEssNoVersion] Configuration Manager version to manage that particular version of [!INCLUDEssNoVersion]. Here are the paths to the last five versions when Windows is installed on the C drive.

Version Path
[!INCLUDEssNoVersion] 2019 C:\Windows\SysWOW64\SQLServerManager15.msc
[!INCLUDEssNoVersion] 2017 C:\Windows\SysWOW64\SQLServerManager14.msc
[!INCLUDEssNoVersion] 2016 C:\Windows\SysWOW64\SQLServerManager13.msc
[!INCLUDEssSQL14] C:\Windows\SysWOW64\SQLServerManager12.msc
[!INCLUDEssSQL11] C:\Windows\SysWOW64\SQLServerManager11.msc

Note

Because [!INCLUDEssNoVersion] Configuration Manager is a snap-in for the [!INCLUDEmsCoName] Management Console program and not a stand-alone program, [!INCLUDEssNoVersion] Configuration Manager does not appear as an application in newer versions of Windows.

  • Windows 10:
    To open [!INCLUDEssNoVersion] Configuration Manager, on the Start Page, type SQLServerManager13.msc (for [!INCLUDEsssql15-md]). For other versions of [!INCLUDEssNoVersion], replace 13 with the corresponding number. Clicking SQLServerManager13.msc opens the Configuration Manager. To pin the Configuration Manager to the Start Page or Task Bar, right-click SQLServerManager13.msc, and then click Open file location. In the Windows File Explorer, right-click SQLServerManager13.msc, and then click Pin to Start or Pin to taskbar.
  • Windows 8:
    To open [!INCLUDEssNoVersion] Configuration Manager, in the Search charm, under Apps, type SQLServerManager<version>.msc such as SQLServerManager13.msc, and then press Enter.

[!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion] tools and to provide enhanced control and manipulation over the selected SQL services of the [!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion] Configuration Manager, see Connect to Another Computer (SQL Server Configuration Manager).

Managing Services

Use [!INCLUDEssNoVersion] Configuration Manager to start, pause, resume, or stop the services, to view service properties, or to change service properties.

Use [!INCLUDEssNoVersion] Configuration Manager to start the [!INCLUDEssDE] using startup parameters. For more information, see Configure Server Startup Options (SQL Server Configuration Manager).

Changing the Accounts Used by the Services

Manage the [!INCLUDEssNoVersion] services using [!INCLUDEssNoVersion] Configuration Manager.

Important

Always use [!INCLUDEssNoVersion] tools such as [!INCLUDEssNoVersion] Configuration Manager to change the account used by the [!INCLUDEssNoVersion] or [!INCLUDEssNoVersion] Agent services, or to change the password for the account. In addition to changing the account name, [!INCLUDEssNoVersion] Configuration Manager performs additional configuration such as setting permissions in the Windows Registry so that the new account can read the [!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion] portion of the registry the service may not start properly.

As an additional benefit, passwords changed using [!INCLUDEssNoVersion] Configuration Manager, SMO, or WMI take affect immediately without restarting the service.

Manage Server & Client Network Protocols

[!INCLUDEssNoVersion] Configuration Manager allows you to configure server and client network protocols, and connectivity options. After the correct protocols are enabled, you usually do not need to change the server network connections. However, you can use [!INCLUDEssNoVersion] Configuration Manager if you need to reconfigure the server connections so [!INCLUDEssNoVersion] 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.

[!INCLUDEssNoVersion] 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.

[!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion] 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

[!INCLUDEssNoVersion] supports Shared Memory, TCP/IP, and Named Pipes protocols. For information about choosing a network protocols, see Configure Client Protocols. [!INCLUDEssNoVersion] does not 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 [!INCLUDEssNoVersion]. You cannot use [!INCLUDEssNoVersion] Configuration Manager to configure the WinSock proxy. To configure the WinSock proxy, see your ISA Server documentation.

Related Tasks

Managing Services How-to Topics (SQL Server Configuration Manager)

Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service

Start, Stop, or Pause the SQL Server Agent Service

Set an Instance of SQL Server to Start Automatically (SQL Server Configuration Manager)

Prevent Automatic Startup of an Instance of SQL Server (SQL Server Configuration Manager)