无法从应用程序连接SQL数据库，求助排查解决方法

Hey there, sorry you’ve been stuck on this frustrating connection issue for two days—let’s walk through practical, actionable steps to get your app connected to SQL Server:

• Confirm the SQL Server instance is running
  Open the Windows Services app (launch via services.msc in the Run dialog), locate the SQL Server (INSTANCE_NAME) service, and check that its status is Running. If you’re using a named instance (like SQLEXPRESS), make sure the SQL Server Browser service is also active—it helps resolve named instances over the network.

• Audit your connection string for mistakes
  Typos or incorrect formatting here are the #1 culprit:

  • For default instances, use Windows Auth: Server=localhost;Database=YourDBName;Trusted_Connection=True;
  • For named instances, the server name should look like .\SQLEXPRESS or YOUR_MACHINE_NAME\SQLEXPRESS
  • If using SQL Auth, verify the username/password are correct: Server=localhost;Database=YourDBName;User Id=YourLogin;Password=YourPass;
  • Double-check the database name is spelled exactly as it exists in SQL Server

• Test basic network connectivity

  • Run ping YOUR_SERVER_ADDRESS (e.g., ping localhost) to confirm the server is reachable
  • Use telnet YOUR_SERVER_ADDRESS 1433 (default SQL port) to check if the port is open. If this fails, your Windows Firewall (or network firewall) is blocking traffic—add an inbound rule for port 1433, or temporarily disable the firewall to test (re-enable it immediately after!)

• Enable remote connections in SQL Server settings

  1. Open SQL Server Management Studio (SSMS), right-click your instance → Properties → Connections
  2. Check the box for Allow remote connections to this server
  3. Open SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for INSTANCE_NAME
  4. Enable the TCP/IP protocol, then double-click it to set the TCP port to 1433 under the IP Addresses tab (look for the IPAll section)
  5. Restart the SQL Server service to apply changes

• Verify authentication mode matches your setup
  If you’re using SQL Server logins (not Windows Auth):

  1. Right-click your instance in SSMS → Properties → Security
  2. Select SQL Server and Windows Authentication mode
  3. Restart the SQL Server service, then confirm your SQL login has permissions to access the target database

• Test connection with SSMS first
  Try connecting to SQL Server using the exact same server name, authentication method, and credentials in SSMS. If SSMS can’t connect, the issue is with the SQL Server setup. If SSMS works, the problem is in your app code or connection string—check for hardcoded errors, environment variable mismatches, or framework-specific formatting quirks.

内容的提问来源于stack exchange，提问作者Mark Riley