SCM Services - Prevent Automatic Startup of an Instance

Applies to: SQL Server

This topic describes how prevent an instance of SQL Server from starting automatically in SQL Server by using SQL Server Configuration Manager. SQL Server is normally configured to start automatically. You can change that by setting the start mode for the instance to manual.

Using SQL Server Configuration Manager

To prevent automatic startup of an instance of SQL Server

  1. On the Start menu, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager.

    Note

    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 and Windows 11:
      To open SQL Server Configuration Manager, on the Start Page, type SQLServerManager13.msc (for SQL Server 2016 (13.x)). For other versions of SQL Server replace 13 with the appropriate 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 SQL Server Configuration Manager, in the Search charm, under Apps, type SQLServerManager<version>.msc such as SQLServerManager13.msc, and then press Enter.
  2. In SQL Server Configuration Manager, expand Services, and then click SQL Server.

  3. In the details pane, right-click MSSQLServer, and then click Properties.

  4. In the SQL Server <instancename> Properties dialog box, on the Service tab, in the General box, set the value of Start Mode to Manual.

  5. Click OK to close the SQL Server <instancename> Properties dialog box, and then close SQL Server Configuration Manager.

See Also

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