5 Different Ways to Start SQL Server Services

Every SQL Server DBA has been there: a service stops responding, and the fastest path back to production is a restart. Knowing multiple methods to start SQL Server services gives you flexibility depending on the situation, whether you have GUI access, remote connectivity, or only a command prompt. Here are five proven methods for starting a standalone SQL Server instance, along with when each one works best.

Object Explorer in SSMS (SQL Server Management Studio)

You can start a remote SQL Server directly from SSMS Object Explorer by right-clicking the server name and selecting Start, Pause, Resume, or Stop. This works for both local and remote servers, provided you have an active connection and the appropriate remote-service permissions.

If the instance is already stopped and you are not connected, you cannot use this method to start it. Stopping the service and then closing SSMS creates the same problem: you lose the connection needed to issue a Start command. For that scenario, use one of the other four methods below.

Windows Services

This is the method most DBAs reach for first. Open the Services applet by pressing Windows + R and typing services.msc, or navigate through Start, Programs, Administrative Tools, Services.

Find the MSSQLServer service in the list. For a named instance, look for SQL Server (InstanceName). For example, a named instance called SQL2014 appears as SQL Server (SQL2014).

Right-click the service and select the action you need: Start, Stop, Pause, or Resume. To add startup parameters, open the service properties and enter them in the Start parameters field before clicking Start.

The Net Start command

When you need a command-line approach (or want to script a restart), net start gets the job done. Open a command prompt with administrator privileges and type:

To start a named instance, use the MSSQL$instancename format:

You can append startup parameters directly to the command.  To start SQL Server in single-user mode:

To enable a trace flag (for example, Trace Flag 3608):

Multiple startup parameters can be combined on the same line:

Using Sqlservr.exe executable

The sqlservr.exe executable starts SQL Server directly from the binary directory, bypassing the Windows service layer. This method is useful when you need to enable debugging, troubleshoot startup failures, or run SQL Server interactively in a console window.

Navigate to the binn directory where SQL Server stores its binary files. Run the executable with the -s parameter followed by the instance name:

For named instances, replace MSSQLSERVER with the instance name. For a complete list of startup parameters, refer to the Microsoft documentation on sqlservr.exe.

SQL Server Configuration Manager

SQL Server Configuration Manager is the purpose-built tool for managing SQL Server services, and it is the recommended method when you need full control over service accounts, startup types, and protocol configuration alongside start and stop operations.

Open it through Start, Programs, Microsoft SQL Server (version), Configuration Tools, SQL Server Configuration Manager. Click SQL Server Services in the left pane to display all SQL Server services on the right. Right-click SQL Server (MSSQLServer) and choose the action you need. A green icon next to the service name confirms the service is running.

One limitation: SQL Server Configuration Manager cannot manage services on remote machines. For remote service management, use SSMS Object Explorer or Windows remote administration tools.

Picking the Right Method

Each of these five methods serves a different situation. 

SSMS Object Explorer is the fastest option when you already have a connection open. Windows Services is the go-to for most daily administration. The net start command is ideal for scripting and automation. Sqlservr.exe provides direct control for debugging and troubleshooting. SQL Server Configuration Manager is the most complete tool, combining service management with configuration options in a single interface.

Knowing all five methods ensures you can restart SQL Server services regardless of whether you have GUI access, an active SSMS connection, or only a command prompt.

FAQ

Which method is the fastest way to restart SQL Server services?

If you already have SSMS open and connected, right-clicking the server in Object Explorer is the quickest option. If you are working from the command line, net start mssqlserver takes seconds. For most DBAs, Windows Services (services.msc) is the everyday default because it requires no prior connection to the instance.

Can I start a remote SQL Server instance from my local machine?

Yes, but only through SSMS Object Explorer. The other four methods (Windows Services, net start, sqlservr.exe, and SQL Server Configuration Manager) only manage services on the local machine. For remote service management without SSMS, you would need Windows remote administration tools or PowerShell remoting.

What if SQL Server will not start at all?

Start sqlservr.exe directly from the command line. Running SQL Server outside the Windows service layer displays startup errors in the console window, making it easier to diagnose configuration issues, missing databases, or corrupt system files. You can also add the -m flag to start in single-user mode for recovery operations.

How do I start a SQL Server named instance?

The syntax differs by method. In Windows Services, look for SQL Server (InstanceName). With net start, use net start MSSQL$InstanceName. With sqlservr.exe, use sqlservr.exe -s InstanceName. In SSMS and SQL Server Configuration Manager, named instances appear by name in the interface.

Can I add startup parameters when starting SQL Server?

Yes, through Windows Services (in the service properties dialog), the net start command (appended to the command line), and sqlservr.exe (as command-line arguments). SSMS Object Explorer does not support adding startup parameters at start time. SQL Server Configuration Manager lets you configure startup parameters permanently through the service properties.