SQL Server Configuration Manager

SQL Server Configuration Manager is a Microsoft Management Console snap-in for SQL Server service and network settings. It is not SQL Server Management Studio. SSMS lets you connect to SQL Server, run queries, manage objects, check jobs, and do day-to-day database work. Configuration Manager handles the Windows-side SQL Server settings that often affect whether the instance starts and whether clients can connect.

The fastest way to open it is to run the matching SQLServerManagerXX.msc file. The number depends on the SQL Server version. SQL Server 2022 uses SQLServerManager16.msc. SQL Server 2019 uses SQLServerManager15.msc. Newer Windows versions may not show Configuration Manager as a normal Start menu app, so the MSC file is the cleaner route.

Start with the SQL Server host, not a random admin workstation. If the Database Engine runs on a server and your laptop only has SSMS, Configuration Manager may not be present locally.

Use one of these paths: search the Start menu for the matching MSC file, open Run and type the MSC file name, browse to C:\Windows\SysWOW64, or open mmc.exe and add the SQL Server Configuration Manager snap-in.

Pinning the MSC file can save time on servers you manage often. Still, check the file name before assuming it matches the instance. A server can have older and newer SQL Server components installed side by side.

The MSC number follows the SQL Server major version. It does not follow the SSMS major version and it does not tell you which cumulative update is installed.

Most missing-tool cases come from one of two mistakes: SSMS was installed without SQL Server components, or the search is happening on the wrong machine. Configuration Manager is tied to the SQL Server installation. It is not a separate SSMS feature.

This is also why copying an MSC file from another server is a bad troubleshooting shortcut. The file is only the console entry point. The useful work depends on the SQL Server installation, WMI registration, local permissions, and the services present on that machine.

If the server really does not have the required SQL Server components, get the installer or media from Microsoft's SQL Server downloads page. Use that to install or repair SQL Server on the right machine. Do not treat it as a separate Configuration Manager download.

Use Configuration Manager when the change is about SQL Server as a Windows service or about how SQL Server listens for connections. It is the right tool for service accounts, service startup behavior, startup parameters, SQL Server Browser, and server network protocols.

It is not where you create tables, tune indexes, check query plans, or manage database objects. Use SSMS for that. The split matters because people often install one tool and expect it to include the other.

For SQL Server and SQL Server Agent service accounts, use SQL Server Configuration Manager. It handles SQL-specific settings that plain Windows Services does not always handle. That includes permissions, registry access, and related Windows local security store updates that the Database Engine needs after the account changes.

Changing the account in Windows Services can leave the Database Engine unable to read required SQL Server settings. The ugly version of this problem is a service that starts only after someone adds the service account to local Administrators. That is not a good fix. It usually means the account change was done without the SQL-specific work around it.

In real environments, also check file access, backup locations, SQL Agent jobs, proxies, linked services, SPNs, Kerberos use, group policy, and restart timing before changing an account. Service account work is security work and availability work at the same time.

To enable TCP/IP, open SQL Server Configuration Manager, expand SQL Server Network Configuration, select Protocols for the target instance, right-click TCP/IP, and choose Enable. Then restart the SQL Server service for that instance. For a named instance, also restart SQL Server Browser.

Do not stop at the Enable button. Check the IP Addresses tab, especially IPAll, TCP Dynamic Ports, and TCP Port. If the instance is named, confirm how clients find it. If the server firewall blocks the active port, enabling TCP/IP will not be enough.

If a connection problem started after a move, patch, restore, or server rename, compare the instance name, listener name, DNS record, and port before changing more settings. The failed connection string often points at an old name or a named instance that no longer resolves the way the application expects.

For production, record the old values first. A protocol change can affect application servers, reports, linked servers, ETL jobs, monitoring probes, backup tools, and vendor integrations.

SQL Server connectivity is not just "TCP/IP enabled". The instance needs to listen on a port, the firewall must allow that port, and clients must know where to connect.

Dynamic ports can work, but they are awkward for locked-down servers because the active port can change after restart. A static port is easier to document and easier to allow through a firewall. Named instances often use SQL Server Browser so clients can discover the current port from the instance name.

Client aliases let a computer connect to SQL Server through a local alias instead of the real server and instance name. They can be useful during migrations, application moves, or older vendor setups where connection strings are hard to change.

Treat aliases carefully. They can hide where an application really connects, and they are easy to forget during server moves. Check both 32-bit and 64-bit client configuration if an older application behaves differently from a modern tool.

Microsoft notes that SQL Server 2022 and later do not support creating aliases in SQL Server Configuration Manager. Use SQL Server Client Network Utility for that work on current versions.

The tool is small, but the settings behind it are not harmless. Most problems come from version confusion, WMI trouble, changing the wrong instance, or forgetting that protocol changes need a service restart.

If you are only looking, look. If you are changing service accounts, protocols, ports, or startup parameters, slow down and capture the current state first. Configuration Manager changes can be simple, but they sit close to service availability.