📝 Overview
SQL Server is the database engine that the software runs on. If you open the software and see a message that SQL Server has not started or cannot be started, this article will help you get it running again. Common causes include a power outage, a Windows update, or an error during the Windows startup process.
🛠️ Before You Begin
Restart your computer first and try opening the software again. SQL Server may simply not have started properly during the Windows startup process.
If you still see the same message after restarting, continue with the steps below.
💡 Restart first: Restarting your computer resolves this issue in many cases without needing to start SQL Server manually.
▶️ Starting SQL Server Manually
Learn how to manually start SQL Server using SQL Server Configuration Manager.
Open SQL Server Configuration Manager. You can find it two ways:
Go to Start Menu, then search for SQL Server [year] Configuration Manager (where [year] matches your installed SQL Server version, e.g. 2012), or
Go to Start Menu > All Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager.
In the left-hand pane, click SQL Server Services.
In the right-hand pane, locate SQL Server Browser. If it is not showing Running in the State column, right-click on it.
Choose Start from the menu.
Right-click on the instance of SQL Server that is not running. It should be displaying Stopped in the State column.
Choose Start from the menu.
If the instance starts, close SQL Server Configuration Manager and open the software again. It should connect to your database normally. If it does not start, continue to the Troubleshooting section below.
🔍 Locating SQL Server Configuration Manager on Windows 10
Learn how to find SQL Server Configuration Manager if it does not appear when searching your Start Menu.
Click here to learn how to locate SQL Server Configuration Manager
Click here to learn how to locate SQL Server Configuration Manager
Go to Start Menu > File Explorer.
Navigate to C:\Windows\SysWOW64 (this path is the same on most computers).
Locate the file named SQLServerManagerX.msc — the number in place of X matches your installed SQL Server version.
Double-click the file to open Configuration Manager, then follow steps 2–7 in the Starting SQL Server Manually section above.
⚠️ Troubleshooting
Find solutions to common issues when starting SQL Server.
SQL Server still won't start after following these steps: It may need to be reinstalled. Reinstalling SQL Server should be completed with help from our support team. Visit our Support Options article to find the best way to reach us.
You don't see an instance of SQL Server in Configuration Manager at all: This may mean SQL Server was never installed on this computer. Contact support for help determining next steps.
⚠️ Don't keep retrying: If SQL Server won't start after following these steps, contact support rather than repeating the process multiple times.
❓ Frequently Asked Questions (FAQs)
Find answers to common questions or additional details that may not be covered in the main instructions.
Why does SQL Server sometimes fail to start on its own?
Click the arrow to view the answer
Click the arrow to view the answer
This can happen after a power outage, a Windows update, or an error during the Windows startup process that prevents SQL Server from starting automatically.
What should I try before manually starting SQL Server?
Click the arrow to view the answer
Click the arrow to view the answer
Restart your computer first and try opening the software again. This resolves the issue in many cases without needing to start SQL Server manually.
I can't find SQL Server Configuration Manager in my Start Menu. What do I do?
Click the arrow to view the answer
Click the arrow to view the answer
On some Windows 10 computers, SQL Server Configuration Manager may not appear in your Start Menu. See the Locating SQL Server Configuration Manager section above to find it manually.
What if SQL Server still won't start after these steps?
Click the arrow to view the answer
Click the arrow to view the answer
SQL Server may need to be reinstalled. Reach out to our support team for help, as reinstallation should be completed with their assistance.