Merge branch 'MicrosoftDocs:main' into 250711-arc-sql-july

Author: MikeRayMSFT

docs/database-engine/configure-windows/database-engine-service-startup-options.md

@@ -3,7 +3,7 @@ title: Database Engine Service Startup Options
 description: Become familiar with SQL Server Database Engine startup options. View tips on how to use them, and learn about the purpose of each option.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 06/11/2025
+ms.date: 07/15/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
@@ -60,7 +60,7 @@ The following screenshot shows the Startup Parameters tab in the SQL Server Prop
 | `-f` | Starts an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] with [minimal configuration](start-sql-server-with-minimal-configuration.md). This is useful if the setting of a configuration value (for example, over-committing memory) prevents the server from starting. Starting [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in minimal configuration mode places [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode. For more information, see the description for `-m` that follows. |
 | `-k<decimal-number>` | This startup parameter limits the number of checkpoint I/O requests per second, where the `<decimal-number>` represents the checkpoint speed in MB per second. Changing this value can affect the speed of taking backups, or going through the recovery process so proceed with caution. That is, if the value you specify for the parameter is too low, you might experience a longer recovery time and backups might take a slightly longer time to finish, because a checkpoint process that a backup initiates is also delayed.<br /><br />Instead of using this parameter, you use the following methods to help eliminate I/O bottlenecks on your system:<br /><br />- Provide appropriate hardware to sustain I/O requests that are posted by SQL Server<br /><br />- Perform sufficient application tuning |
 | `-m` | Starts an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode. When you start an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode, only a single user can connect, and the `CHECKPOINT` process isn't started. `CHECKPOINT` guarantees that completed transactions are regularly written from the disk cache to the database device. (Typically, this option is used if you experience problems with system databases that should be repaired.) Enables the `sp_configure` allow updates option. By default, allow updates is disabled. Starting [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode enables any member of the computer's local Administrators group to connect to the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] as a member of the **sysadmin** fixed server role. For more information, see [Connect to SQL Server when system administrators are locked out](connect-to-sql-server-when-system-administrators-are-locked-out.md). For more information about single-user mode, see [Single-user mode for SQL Server](start-sql-server-in-single-user-mode.md). |
-| `-mClient Application Name` | Limits the connections to a specified client application. For example, `-mSQLCMD` limits connections to a single connection and that connection must identify itself as the **sqlcmd** utility. Use this option when you're starting [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode and an unknown client application is taking the only available connection. Use `"Microsoft SQL Server Management Studio - Query"` to connect with the SSMS Query Editor. The SSMS Query Editor option can't be configured by using [!INCLUDE [ssNoVersion_md](../../includes/ssnoversion-md.md)] Configuration Manager because it includes the dash character, which is rejected by the tool.<br /><br />Client Application Name is case sensitive. Double quotes are required if the application name contains spaces or special characters.<br /><br />**Examples when starting from the command line:**<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -m"Microsoft SQL Server Management Studio - Query"`<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -mSQLCMD`<br /><br />**Security note:** Don't use this option as a security feature. The client application provides the client application name, and can provide a false name as part of the connection string. |
+| `-mClient Application Name` | Limits the connections to those using a specific application name in the client connection string. For example, `-mSQLCMD` limits connections to a single connection from the **sqlcmd** utility. Use this option when you're starting [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode and an unknown client application is taking the only available connection. Use `"Microsoft SQL Server Management Studio - Query"` to connect with the SQL Server Management Studio (SSMS) Query Editor. The SSMS Query Editor option can't be configured by using [!INCLUDE [ssNoVersion_md](../../includes/ssnoversion-md.md)] Configuration Manager because it includes the dash (`-`) character.<br /><br />Client Application Name is case sensitive. Double quotes are required when [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is started from the command line if the application name contains spaces or special characters. Don't use double quotes in [!INCLUDE [ssNoVersion_md](../../includes/ssnoversion-md.md)] Configuration Manager.<br /><br />For more information about setting startup options in SQL Server Configuration Manager, see [Use SQL Server Configuration Manager](scm-services-configure-server-startup-options.md#SSMSProcedure).<br /><br />**Examples when starting from the command line:**<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -m"Microsoft SQL Server Management Studio - Query"`<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -mSQLCMD`<br /><br />**Security note:** Don't use this option as a security feature. The client application provides the client application name, and can provide a false name as part of the connection string. |
 | `-n` | Doesn't use the Windows application log to record [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] events. If you start an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] with `-n`, we recommend that you also use the `-e` startup option. Otherwise, [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] events aren't logged. |
 | `-s` | Allows you to start a named instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Without the `-s` parameter set, the default instance tries to start. You must switch to the appropriate `BINN` directory for the instance at a command prompt before starting `sqlservr.exe`. For example, if Instance1 were to use `\mssql$Instance1` for its binaries, the user must be in the `\mssql$Instance1\binn` directory to start `sqlservr.exe -s instance1`. |
 | `-T <trace-number>` | Indicates that an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] should be started with a specified trace flag (`<trace-number>`) in effect. Trace flags are used to start the server with nonstandard behavior. For more information, see [DBCC TRACEON - Trace Flags](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md).<br /><br />**Important:** When specifying a trace flag with the `-T` option, use an uppercase `T` to pass the trace flag number and no space between the `-T` option and the number of the trace flag. A lowercase `t` is accepted by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], but this sets other internal trace flags that are required only by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] support engineers. (Parameters specified in the Control Panel startup window aren't read.) |

docs/database-engine/configure-windows/scm-services-configure-server-startup-options.md

@@ -1,9 +1,9 @@
 ---
-title: "Configure server startup options (SQL Server Configuration Manager)"
+title: "Configure Server Startup Options (SQL Server Configuration Manager)"
 description: Learn how to set options that the SQL Server Database Engine uses when it starts. View limitations and restrictions on making changes to startup parameters.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 07/26/2024
+ms.date: 07/15/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: how-to
@@ -29,7 +29,7 @@ This article describes how to configure startup options that are used every time
 
 On a cluster, changes must be made on the active server when [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is online, which take effect when the [!INCLUDE [ssDE](../../includes/ssde-md.md)] is restarted. The registry update of the startup options on the other node will occur upon the next failover.
 
-Starting with [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], when you set the **Start Mode** for a [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] service to *Automatic* in Configuration Manager, the service starts in *Automatic (Delayed Start)* mode instead, even though the **Start Mode** shows as *Automatic*.
+In [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions, when you set the **Start Mode** for a [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] service to *Automatic* in Configuration Manager, the service starts in *Automatic (Delayed Start)* mode instead, even though the **Start Mode** shows as *Automatic*.
 
 ## Permissions
 
@@ -39,7 +39,9 @@ Configuring server startup options is restricted to users who can change the rel
 
 - The domain account that is used by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], if the [!INCLUDE [ssDE](../../includes/ssde-md.md)] is configured to run under a domain account.
 
-## <a id="SSMSProcedure"></a> Use SQL Server Configuration Manager
+<a id="SSMSProcedure"></a>
+
+## Use SQL Server Configuration Manager
 
 ### Configure startup options
 
@@ -69,7 +71,11 @@ Configuring server startup options is restricted to users who can change the rel
 1. Restart the [!INCLUDE [ssDE](../../includes/ssde-md.md)].
 
    > [!WARNING]  
-   > After you're finished using single-user mode, in the Startup Parameters box, select the **-m** parameter in the **Existing Parameters** box, and then select **Remove**. Restart the [!INCLUDE [ssDE](../../includes/ssde-md.md)] to restore [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to the typical multi-user mode.
+   > After you're finished using single-user mode, in the Startup Parameters box, select the `-m` parameter in the **Existing Parameters** box, and then select **Remove**. Restart the [!INCLUDE [ssDE](../../includes/ssde-md.md)] to restore [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to the typical multi-user mode.
+
+- Don't use double quotes around startup parameter values even if they contain spaces or special characters.
+
+- [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager doesn't support dashes (`-`) and slashes (`/`) in startup parameter values.
 
 ## Related content