Connect with us

TECHNOLOGY

How to Restart SQL Server: A Step-by-Step Windows Guide

How to restart SQL Server: pause the engine so open work can finish, stop it so each database checkpoints, then start that same instance again.

Published

on

How to restart SQL Server on Windows is a stop and a start of one Windows service, and that service is a whole instance. Every database on it has to start again, and every session connected to it drops when the service stops.

Pause the Database Engine when people are still working in it. New logins stop, work already running can finish, and the stop that follows can write a checkpoint in each database so recovery has a known point to start from. SHUTDOWN WITH NOWAIT skips that checkpoint. Configuration Manager, SSMS, an administrator command prompt, and PowerShell can all restart the service once the name in the list matches the instance you mean.

The steps below name the three services people mix up, show the pause, and walk through each tool, including what to change when the service will not come back. They apply to SQL Server installed on Windows.

Which SQL Server Service Are You Restarting?

SQL Server components run as Windows services, with no window of their own. A computer holds one default Database Engine at most, plus every named instance you installed beside it. The default engine is listed as SQL Server (MSSQLSERVER). A named instance is listed as SQL Server (instancename). SQL Server Express is installed as SQL Server (SQLEXPRESS).

SQL Server Agent runs the scheduled jobs and alerts for one instance, and it is not included in every edition. SQL Server Browser is shared: one Browser service on the computer answers lookup requests for every instance installed there. Restarting one engine does not replace Browser, and restarting Browser does not restart any engine.

Service Name in the list Name you type Pause
Database Engine, default SQL Server (MSSQLSERVER) MSSQLSERVER Yes
Database Engine, named SQL Server (instancename) MSSQL$instancename Yes
SQL Server Express SQL Server (SQLEXPRESS) MSSQL$SQLEXPRESS Yes
SQL Server Agent, default SQL Server Agent (MSSQLSERVER) SQLSERVERAGENT No
SQL Server Agent, named SQL Server Agent (instancename) SQLAgent$instancename No
SQL Server Browser SQL Server Browser SQLBrowser Yes

Read the name in parentheses before you click. Restarting SQL Server (SQLEXPRESS) leaves a default instance alone, and restarting MSSQLSERVER leaves every named instance alone. Agent for a named instance is its own row, SQL Server Agent (instancename), not the Agent row for the default instance. The service name you type for a named engine is MSSQL$instancename, with the instance name after the dollar sign.

Pause the Database Engine Before You Stop It

Pause is the step a plain Restart click skips, and it is the one that decides who is still inside when the stop begins. While the Database Engine is paused, users who are already connected can keep working until their connection breaks, and new users cannot connect. Resume lets the engine accept new connections again. Use the pause when you want current transactions to finish before the service stops.

WHAT PAUSE CHANGES

  • Who stays in: Sessions that are already open can keep working until they disconnect.
  • Who stays out: New users cannot connect to that Database Engine while it is paused.
  • What cannot pause: SQL Server Agent cannot be paused or resumed.

In Configuration Manager or SSMS, pause the Database Engine and let the sessions you care about finish. When that work is done, stop the service, then start it. If a session will not end, you can still stop the instance. A stop from Configuration Manager, from net stop, or from Services writes a checkpoint in each database. A stop with SHUTDOWN WITH NOWAIT does not, which is the difference covered with the SHUTDOWN statement below.

Stop SQL Server Agent for that instance before a planned engine stop if you do not want jobs to start during the drain, then look at Agent again after the engine is running. In Configuration Manager a green arrow means started, a red square means stopped, and two vertical blue lines mean paused. Actions that do not fit the current state are not offered, so Start is missing when the service is already running.

How to Restart SQL Server in Configuration Manager

SQL Server Configuration Manager is the snap-in built to start, stop, pause, resume, and restart these services, and to hold startup options and the service account. Because it is a Microsoft Management Console snap-in rather than a normal app, Windows 10 and Windows 11 often hide it from the Start menu. The reliable open is the version file.

THE SNAP-IN FILE FOR YOUR VERSION

  • SQL Server 2025: SQLServerManager17.msc
  • SQL Server 2022: SQLServerManager16.msc
  • SQL Server 2019: SQLServerManager15.msc
  • SQL Server 2017: SQLServerManager14.msc
  • SQL Server 2016: SQLServerManager13.msc
  • SQL Server 2014: SQLServerManager12.msc
  • SQL Server 2012: SQLServerManager11.msc

Each file sits in C:\Windows\SysWOW64\. Type the file name on the Start menu. You can also right-click it, choose Open file location, and pin it to the taskbar so the next restart does not start with a search.

With the snap-in open, select Yes if User Account Control appears, then use the service list.

  1. In the left pane, select SQL Server Services.
  2. Right-click SQL Server (MSSQLSERVER), or SQL Server and the name of your instance.
  3. Select Pause while sessions are still active. When they are finished, select Stop, then select Start. Select Restart when you want that stop and start as one action.
  4. Select OK to close Configuration Manager.

Browser and Agent are on the same list. Right-click SQL Server Browser, SQL Server Agent (MSSQLSERVER), or SQL Server Agent (instancename), then choose the action. Skip Pause on Agent, because that service cannot pause. On a failover cluster, Configuration Manager can show the clustered instance, but starting and stopping the Database Engine belongs to Cluster Administrator.

On SQL Server 2022 and later, setting Start Mode to Automatic in Configuration Manager starts the service as Automatic (Delayed Start), even though Start Mode still reads Automatic. If the instance is slow to appear after a reboot, that delayed start is the first check, before you treat the service as failed. Choose Manual on the Service tab when this instance should stay down until someone starts it, and Automatic when it should come up with Windows.

Change the account the service runs under in this tool, not in the Windows Services list. Other tools can change the account name and skip the rest of the setup, so the service can fail on the next start because it cannot read its settings. The registry permissions for the service account are part of what Configuration Manager writes when the account changes.

Stop and Start the Instance in SSMS

When you are already connected, Object Explorer can send the same service actions. Connect to the Database Engine, right-click that instance, and select Start, Stop, Pause, Resume, or Restart. Accept User Account Control if it appears, then select Yes when SSMS asks you to confirm the action.

That Object Explorer path begins with a connection, so it cannot be how you start an instance that is already stopped. Registered Servers is the SSMS path for that case. Right-click the registered instance, point to Service Control, and select Start, Stop, Pause, Resume, or Restart. The same Yes prompts apply.

SQL Server Agent in Object Explorer offers Start, Stop, and Restart, and it does not offer Pause. After the engine shows a green arrow, open the Agent node and start it if jobs for that instance should run and the icon is still a red square.

The confirmation dialog can open on a monitor you are not watching. If the icon never changes, check the other display before you send the restart again, or you will spend the outage waiting on a prompt that is already on screen.

Stop and Start SQL Server From the Command Prompt

Open the command prompt with Run as administrator. By default, only members of the local administrator group can start, stop, pause, resume, or restart the service, and a normal prompt is refused. SHUTDOWN, covered in the next section, is a separate check inside SQL Server and does not replace this Windows check.

For the default instance, either command starts the engine. Use the quoted display name or the short service name:

  • Start: net start "SQL Server (MSSQLSERVER)" or net start MSSQLSERVER
  • Pause: net pause "SQL Server (MSSQLSERVER)" or net pause MSSQLSERVER
  • Stop: net stop "SQL Server (MSSQLSERVER)" or net stop MSSQLSERVER

A planned restart on that default instance is pause, then stop, then start, using the same name each time. For a named instance, put the name from the parentheses into both forms. An instance named SALES is net pause "SQL Server (SALES)" or net pause MSSQL$SALES, then the same text with net stop and net start. Express follows that named pattern: SQL Server (SQLEXPRESS) in quotes, or MSSQL$SQLEXPRESS with no quotes. Quote the display name whenever it contains spaces. The short service name does not need quotes.

Agent on the default instance starts with net start "SQL Server Agent (MSSQLSERVER)" or net start SQLSERVERAGENT. On a named instance the pair is net start "SQL Server Agent (instancename)" or net start SQLAgent$instancename. Browser starts with net start "SQL Server Browser" or net start SQLBrowser. Replace net start with net pause or net stop for those services the same way, except you still cannot pause Agent.

Startup flags on net start use a slash, not a hyphen, with a space before each flag. The example Microsoft prints for a troubled start is net start MSSQLSERVER /f /m, and also net start "SQL Server (MSSQLSERVER)" /f /m. Keep that pair off a normal restart. It is for the case, covered below, where a configuration value stops the service from coming up.

Stop the Database Engine With SHUTDOWN

The net commands and the menus stop the Windows service. If you are already logged into the instance and you want the stop that waits for running statements, run SHUTDOWN from a query window. You need a seat in the sysadmin or serveradmin fixed server role, and you cannot pass that right on to someone else. A Windows administrator who is not in one of those roles can still stop the service from Configuration Manager or with net stop. A sysadmin who is not a local administrator can run SHUTDOWN and still get refused at the service-control prompt.

Run sp_who first when you want the list of current users. sp_who and sp_lock together show active processes and locks, which is the list you are waiting on if you paused so that work could finish.

A clean stop follows how the SHUTDOWN statement stops SQL Server. Logins are disabled except for sysadmin and serveradmin, running Transact-SQL statements and stored procedures are allowed to finish, and a checkpoint is written in every database. That checkpoint is a known point in the log, so there is less recovery work when the instance starts again. The statement to run is SHUTDOWN;

SHUTDOWN WITH NOWAIT skips those steps. SQL Server tries to end user processes and exits without writing a checkpoint in each database. When the instance starts again, incomplete transactions roll back. Use it only when you accept that longer comeback.

Configuration Manager, net stop MSSQLSERVER, net stop MSSQL$instancename, and Services in Control Panel also write a checkpoint in all databases. Pressing Ctrl+C does not, when sqlservr.exe was started from a command prompt instead of as a Windows service. SHUTDOWN only stops the engine. Start the service afterward with Configuration Manager, Registered Servers, net start, or PowerShell.

Start and Stop SQL Server in PowerShell

When the restart has to live in a script, use a SQL Server PowerShell prompt and the ManagedComputer object for that computer. Replace computername with the name of the computer:

CD SQLSERVER:\SQL\computername
$Wmi = (get-item.).ManagedComputer

Then take one service from $Wmi.Services. The default engine is MSSQLSERVER. A named engine is MSSQL$instancename. Agent on the default instance is SQLSERVERAGENT. Agent on a named instance is SQLAGENT$instancename. Browser is SQLBROWSER. The net command prints SQLAgent$instancename for a named Agent, and this provider uses SQLAGENT$instancename. Windows treats those as the same service.

Call Start() or Stop() on that object, then call Refresh() before you read the state. The cached state can still show the old value if you skip the refresh. Print the object before the call and again after Refresh if the script needs to prove the change. A scripted restart of the default engine is Stop(), Refresh(), Start(), Refresh(), on the MSSQLSERVER service, after you have already paused and drained sessions if people are connected.

The same start and stop actions are available to a program through the.NET ServiceController class, which talks to the Windows service by the same service name.

What to Do When SQL Server Will Not Start

On a cluster, bring the Database Engine online with Cluster Administrator. On a standalone server, a refused start leaves a message in the tool you used and an event in the Windows Application log or the System log. Read that message before you add startup flags. Microsoft keeps a separate walkthrough for startup errors on a standalone server, another for the engine and Agent failing together, and another for Agent crashing as it starts.

A Disabled SQL Server Start Mode

In Configuration Manager, select SQL Server Services and find the row. If Start Mode reads Other (Boot, System, Disabled or Unknown), that value means the service is disabled.

  1. Right-click the service and open Properties.
  2. Open the Service tab and confirm Start Mode is Disabled.
  3. Set Start Mode to Manual or Automatic, apply the change, and start the service.

Manual keeps the instance down until someone starts it. Automatic brings it up with Windows, with the delayed-start behavior on SQL Server 2022 and later described above. A disabled service will refuse Start until this tab changes.

What Does Error 1069 Mean for the Service Account?

Error 1069 means the service did not start because the sign-in failed. The Services text reads: “Windows could not start the SQL Server (MSSQLSERVER) service on Local Computer. Error 1069: The service did not start due to a logon failure.” SQL Server Agent raises the same failure when its own account cannot sign in.

  • The right: The account is missing Log on as a service.
  • The account: It is disabled or locked.
  • The password: It is expired or wrong.
  • The domain: It cannot be reached while Windows is starting the service.

Fix the account in Configuration Manager so the registry rights are written with the new name. Editing only the Log On tab inside Windows Services is how this error comes back on the next start.

How to Start SQL Server in Single-User Mode

When a configuration value blocks startup, over-committed memory is the example Microsoft gives, start the default instance with the flags from the service article: net start MSSQLSERVER /f /m. Use slashes. The /f flag starts minimal configuration, and minimal configuration also places SQL Server in single-user mode. The /m flag is single-user mode by itself.

In single-user mode only one user can connect, and the checkpoint process is not started. A member of the computer’s local Administrators group can connect as sysadmin, which is the way back in when the administrators inside SQL Server are locked out. Connect with one Windows session, fix the setting that blocked the start, stop the service, and start it again with no /f and no /m. An instance left in single-user mode refuses every connection after the first.

Common Mistakes When You Restart SQL Server

The service can be running again and the outage can still be longer than the stop, usually because the wrong service moved or a transaction had to be recovered. Check the choice against the instance you meant before you send people back in.

  • Wrong row in the list. SQLEXPRESS, MSSQLSERVER, and a named instance are three services. The parentheses are the instance.
  • A restart meant to cancel a rollback. The unfinished transaction is still there while the database comes back, so you wait again during recovery.
  • A restart meant to speed up one query. Bouncing the service does not show you the statement. Capture that statement before you take the instance down.
  • Agent left stopped. Jobs and alerts for that instance do not run while its Agent service is stopped. Check the Agent icon after the engine arrow is green.
  • Browser restarted after an authentication-mode change. Mixed-mode sign-in is a setting on the Database Engine. Browser only helps clients find instance names.
  • A Yes prompt on another monitor. The service never restarts, and the icon stays where it was.

If you changed the server to mixed-mode authentication, the service that has to start again is the Database Engine for that instance. Pause it first when users are connected, then stop and start that row, not the Browser row.

Frequently Asked Questions

Does Restarting SQL Server Cancel a Rollback?

Restarting SQL Server does not clear a rollback that is already running. If you stop with SHUTDOWN WITH NOWAIT, or you press Ctrl+C on sqlservr.exe that was started in a command window, incomplete transactions roll back when the instance starts again. Let a rollback finish when that wait is the thing you are trying to skip, because recovery runs the same work on the way back up.

Can You Resume a Paused SQL Server From the Command Prompt?

Resume a paused Database Engine in SQL Server Configuration Manager or in SSMS. The net commands Microsoft documents for this job are net start, net pause, and net stop. After you choose Resume, the engine accepts new connections again.

Does a SQL Server Password Change Need a Restart?

A password changed in SQL Server Configuration Manager takes effect immediately, without a restart of the service. A password changed through SQL Server Management Objects or WMI works the same way. Startup parameters are the change that waits, because Configuration Manager writes them for the next start of the Database Engine.

Does Stopping One Instance Stop SQL Server Browser?

No. One SQL Server Browser service on the computer handles lookup requests for every instance installed there. Stopping SQL Server (MSSQLSERVER) or a named instance leaves Browser running. Restart Browser only when that shared service is the one you intend to stop.

Read the name in parentheses, pause the Database Engine if sessions are open, and stop it with Configuration Manager, net stop, or SHUTDOWN so the checkpoint is written. Start that same service, then look for a green arrow on the engine and on SQL Server Agent. A red square means the restart did not finish, and the message on that dialog is the next thing to read.

Harry runs CREATE MORE FLOW, an independent site, as its editor and lead writer, drawing on a decade of journalism that began in reporting and ended up in editing. His process is the same for every piece. A tip or a document comes in, he finds the primary source behind it, whether that is a regulatory filing, a transcript, a dataset he can open or a product he can test himself, and only then does the writing start. Before anything is published, each number is checked against where it came from, quotes are compared with the recording or transcript, and dates are confirmed. That routine serves a global readership across technology, business and news, science and sports, entertainment and lifestyle, travel, auto and gaming. When a mistake gets through, he corrects the article and leaves a dated note explaining the change, under a corrections policy that is published on the site. He reads his own inbox, and readers can reach him at support@createmoreflow.com with tips, documents or complaints.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending