| title | Start SQL Server with Minimal Configuration | ||
|---|---|---|---|
| description | Become familiar with the minimal configuration startup option in SQL Server. See when and how to use it, and learn about how it limits functionality. | ||
| author | rwestMSFT | ||
| ms.author | randolphwest | ||
| ms.date | 08/26/2025 | ||
| ms.service | sql | ||
| ms.subservice | configuration | ||
| ms.topic | conceptual | ||
| helpviewer_keywords |
|
[!INCLUDE SQL Server]
If you have configuration problems that prevent the server from starting, you can start an instance of [!INCLUDE ssNoVersion] by using the minimal configuration startup option. This is the startup option -f. Starting an instance of [!INCLUDE ssNoVersion] with minimal configuration automatically puts the server in single-user mode.
Consider the following conditions when you start an instance of [!INCLUDE ssNoVersion] in minimal configuration mode:
-
Only a single user can connect, and the
CHECKPOINTprocess isn't executed. -
Remote access and read-ahead are disabled.
-
Startup stored procedures don't run.
-
tempdbis configured at the smallest possible size. -
Audit is disabled, but Audit DDL can still be issued. In practice,
-mshould be sufficient for most cases that require SQL Serve Audit reconfiguration. For more information about security in Auditing configuration, see Auditing in SQL Server.
After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
Important
Use the sqlcmd utility and the dedicated administrator connection (DAC) to connect to [!INCLUDE ssNoVersion]. If you use a typical connection, stop the SQL Server Agent service before connecting to an instance of [!INCLUDE ssNoVersion] in minimal configuration mode. Otherwise, the SQL Server Agent service uses the connection, which blocks it.