How Do I Connect SQL Server to Visual Studio? Three Ways — Server Explorer, Object Explorer & Connected Services (2026)

Visual Studio Learn — Wed, 04 Nov 2026 09:36:44 +0000

You connect Visual Studio to SQL Server three ways — Server Explorer for a design-time connection, SQL Server Object Explorer to browse and query the way you would in SSMS, and Connected Services to wire the database into a project so your code can use it. All three are below, click by click, on Visual Studio 2022 17.14.44 with SQL Server 2025 — including the one encryption error that stops almost everyone the first time.

Versions used in this tutorial

Visual Studio 2022 — 17.14.44 (released October 29, 2026)

SQL Server 2025 (17.x) — Enterprise Developer edition (free for development and testing)

SQL Server Management Studio 22.11.3 (for the comparison section)

Microsoft.Data.SqlClient 6.1.7 (the LTS line, supported until August 14, 2028)

On Visual Studio 2026? Same three tools, same clicks — this walkthrough is captured on 2022, which is still fully supported, and everything below works identically in the newer IDE.

Before you start: set up your environment from zero

Nothing here assumes you already have anything installed. We install Visual Studio with the right workloads, a real SQL Server you control, and SSMS — then verify all of them before connecting anything.

Step 1 — Visual Studio 2022 with the data workloads

Download Visual Studio 2022 Community (free) from Microsoft and run the Visual Studio Installer.
On the Workloads tab, tick:
- Data storage and processing — brings SQL Server Data Tools (SSDT) and SQL Server Express LocalDB. Without it, two of the three methods below do not exist in your IDE.
- .NET desktop development — for the demo project in Method 3.
- Optional: Azure development, only for the Azure SQL path in Method 3.
Click Install, launch Visual Studio, and verify: View → SQL Server Object Explorer exists. (Minimums: 64-bit Windows 11, 4 GB RAM — 16 GB recommended — and 20–50 GB free disk for a typical install.)

Step 2 — SQL Server 2025 Developer edition

LocalDB (from Step 1) covers Methods 1 and 3, but Method 2 deserves a real server. New in SQL Server 2025, there are two free Developer editions: Enterprise Developer (every Enterprise feature) and Standard Developer (every Standard feature). Pick Enterprise Developer for a general dev machine; pick Standard Developer when production runs Standard, so no Enterprise-only feature sneaks into your schema. Both are free — no key, no subscription — licensed for development and testing, not production.

On Microsoft's SQL Server downloads page, choose Developer → Enterprise Developer.
Run setup → Installation → New SQL Server standalone installation.
At Instance Configuration, keep the default instance or name yours — write the name down; you will type it into connection dialogs exactly.
At Server Configuration, set the SQL Server Database Engine service to start automatically.
At Database Engine Configuration → Authentication Mode, choose deliberately: Windows authentication mode is enough for this whole post and is the safer default; Mixed Mode additionally enables SQL logins such as sa — pick it only if you actually need them. You are choosing your server's security shape, not ticking a box.
Click Add Current User so your Windows account is a SQL Server administrator, then Install.
Verify in Services: your instance is Running. (Needs Windows 10 or later, 4 GB RAM recommended, 6 GB free disk.)

Step 3 — SSMS 22 (for the comparison later)

Download SQL Server Management Studio 22 (latest: 22.11.3) from Microsoft — a separate free tool, installed through the Visual Studio Installer — and connect it to the same instance. We will put it side by side with Visual Studio near the end.

Step 4 — Verify everything

In a terminal, run sqllocaldb info. You should see MSSQLLocalDB — the automatic LocalDB instance, owned by your Windows user, starting on demand. LocalDB is a lightweight developer edition of SQL Server Express: user mode, no service to manage, Windows-only. The Developer instance is verified in Services above. Two green checks — now the three methods.

Method 1 — Server Explorer: the design-time connection

The oldest way in, and still the fastest way to attach a database to a project for design-time work.

Open View → Server Explorer.
Click Connect to Database in the toolbar (or right-click Data Connections → Add Connection).
In Choose Data Source, select Microsoft SQL Server → OK. (Different source preselected? Use Change.)
In Add Connection: Server name (localdb)\MSSQLLocalDB; Authentication: Windows Authentication; database: pick one from the drop-down.
Click Test Connection. The success message is the fastest honest check that your server name and login are both right.
Click OK and expand the connection under Data Connections to browse tables.

One thing old tutorials never showed: in designer flows, Visual Studio saves this connection's string into your project's configuration (the connectionStrings section of App.config). That string — not the tree node — is what your application actually uses, which is why the decoding section below matters.

Method 2 — SQL Server Object Explorer: SSMS inside Visual Studio

If Server Explorer is a connection, Object Explorer is a workplace. It requires SSDT from Step 1 and deliberately mirrors the SSMS tree.

Open View → SQL Server Object Explorer (shortcut: Ctrl+\, Ctrl+S).
Right-click the SQL Server node → Add SQL Server.
In the Connect dialog, enter your Developer instance's server name (machine name for a default instance, HOST\INSTANCE for a named one), keep Windows Authentication, click Connect.
Expand the instance → Databases — tables, views and stored procedures in the same hierarchy SSMS shows.
Right-click a database → New Query and run real T-SQL:

CREATE TABLE dbo.DemoCustomers (
    CustomerId INT IDENTITY(1,1) PRIMARY KEY,
    FullName NVARCHAR(100) NOT NULL,
    City NVARCHAR(100) NOT NULL
);
INSERT INTO dbo.DemoCustomers (FullName, City) VALUES
(N'Amara', N'Toronto'),
(N'Jonas', N'Berlin'),
(N'Priya', N'Lagos');
SELECT CustomerId, FullName, City FROM dbo.DemoCustomers;

(The companion code folder at the end contains this exact script as setup.sql, so the post, the video and the code can never drift apart.)

Method 3 — Connected Services: wire the database into a project

Methods 1 and 2 connect you to the database. Connected Services connects your project — package references added, connection string stored properly, dependency registered.

In Solution Explorer, right-click the Connected Services node → Add.
Choose SQL Server Database. The Connect to dependency page offers four targets: SQL Server Express LocalDB, SQL Server Database in a local container, SQL Server Database (on-premises, local network), and Azure SQL Database.
Pick SQL Server Express LocalDB → the MSSQLLocalDB instance.
For connection-string storage, choose the local secrets file — never a source file (the decoding section explains why).
Next → Finish. When the wizard completes, it stores the string in the local secrets file from Step 4 and the dependency appears under Service Dependencies. One honest warning from this tutorial's own capture session: on our machine the wizard stopped at that last step — "Failed to configure Secrets store" — twice, and no dependency appeared (see Errors you may hit #7). The connection string itself was never the problem: the companion console app prints the server version and the demo rows with the same string, and Methods 1 and 2 connect with it too. If the wizard stops on your machine, store the string yourself (Error #7 shows how) and carry on.

The same dialog reaches on-premises servers and Azure SQL Database (that path needs the Azure development workload and an Azure account, and since VS 2022 17.12 it uses Microsoft Entra authentication — Visual Studio does not create the Entra admin user on the database for you, so if none exists, sign-in fails there, not in VS).

Visual Studio or SSMS — which do I open?

Not rivals: Microsoft ships both, on separate cadences, for different jobs.

The job	Open
Building the app that uses the database	Visual Studio
Browsing and querying while you code	SQL Server Object Explorer
Wiring a database into a project	Connected Services
Administering the server itself — backups, jobs, logins, configuration	SSMS

SSMS administers the server, whether or not any application exists; Visual Studio's tools live next to your code and its connections become part of your project. You will end up using both — that is the intended workflow. (Thursday's post goes deeper on the SSMS side: backing up and restoring this same database.)

Your connection string, decoded

Everything above eventually produces one line of text. The LocalDB version, keyword by keyword:

Server=(localdb)\MSSQLLocalDB;Database=DemoDb;Integrated Security=true;Encrypt=true;TrustServerCertificate=true;

Server (Data Source) — (localdb)\MSSQLLocalDB for LocalDB; HOSTNAME for a default instance; HOSTNAME\INSTANCE for a named one (the shape for a hosted or on-premises server too); HOSTNAME,1433 pins the TCP port.
Database (Initial Catalog) — the database you land in.
Integrated Security=true — Windows Authentication: no password in the string, and the recommended pattern for development. SQL Authentication uses User Id + Password instead — and then the string is a secret: user secrets or an environment variable, never source control.
Encrypt=true — on by default in modern tooling (error #1 below). Non-negotiable on any network you do not own.
TrustServerCertificate=true — Encrypt's local-dev companion: accept the dev instance's self-signed certificate. Correct at your desk; in production the real fix is a properly trusted certificate, not this switch.

Coming from Python/FastAPI? Same anatomy, ODBC spelling — pyodbc with Microsoft ODBC Driver 18 for SQL Server:

DRIVER={ODBC Driver 18 for SQL Server};SERVER=(localdb)\MSSQLLocalDB;DATABASE=DemoDb;Trusted_Connection=yes;Encrypt=yes;TrustServerCertificate=yes

If you deployed the FastAPI app from an earlier tutorial in this series to Azure App Service, this string is exactly what its configuration needs next.

Errors you may hit

1. "The certificate chain was issued by an authority that is not trusted"

The error that defines connecting to SQL Server in 2026. Since Visual Studio 17.8 the data tools enable Encrypt by default — modern Microsoft.Data.SqlClient does the same — so your connection demands a TLS certificate from a trusted authority. A local dev instance presents a self-signed one, and the connection dies. It is not your server name, not your password, not a broken install.

At your desk: add TrustServerCertificate=true (or tick the equivalent in the Connect dialog) and reconnect. Microsoft's own LocalDB examples use exactly this pair.
In production: install a certificate from a trusted authority. The trust-anything switch is a development tool, full stop.

2. "A network-related or instance-specific error occurred…" (error 40)

Server not found or unreachable. Causes, in order: the instance name is misspelled (the \INSTANCE half especially), or the Database Engine service is stopped. Open Services, confirm the instance is running, re-check the spelling against Step 2.

3. "Login failed for user" (error 18456)

Authentication reached the server and was refused — classically, a SQL login (sa, or one you created) against a server installed in Windows authentication mode only: Mixed Mode was never enabled at setup, or the login does not exist. Fix the Step 2 choice, or create the login under SSMS → Security.

4. "(localdb) … server was not found"

LocalDB itself is missing. The Data storage and processing workload (or the SQL Server Express LocalDB individual component) installs it — a NuGet package does not. Visual Studio Installer → Modify → add it, then confirm with sqllocaldb info.

5. A named instance is unreachable from another machine

Three suspects: TCP/IP disabled in SQL Server Configuration Manager, the SQL Browser service stopped, or the firewall closed on port 1433. Enable, start, open, restart the instance, retest.

6. Python: "Data source name not found and no default driver specified"

pyodbc cannot find the driver your string names. Install Microsoft ODBC Driver 18 for SQL Server, then copy its name into DRIVER={...} character for character — the braces and exact spacing are part of the name.

7. Connected Services: "Failed to configure Secrets store"

Method 3's wizard can fail at its last step: the progress dialog ends with "Failed to configure Secrets store" and "Failed to configure dependency SQL Server Database", and no dependency appears under Service Dependencies. This is not hypothetical — it happened on this tutorial's own capture machine (Visual Studio Community 2022 17.14.44, November 3, 2026), twice in a row, and it persisted after running dotnet user-secrets init in the project and restarting Visual Studio, the two fixes most often suggested for it.

The important part: the failure is in the wizard's secrets-store step, not in your connection. The connection string itself is unaffected — the exact same string connects fine through Server Explorer (Method 1), SQL Server Object Explorer (Method 2), and the companion console app, which is how this tutorial's demo was verified end to end. If you hit it:

Do not debug your server, your login or your string — test the same string in Method 1 first; if it connects there, the database side is proven.
Store the string yourself instead: add it to your user secrets (dotnet user-secrets set "ConnectionStrings:DatabaseConnection" "...") or an environment variable, and let your code read it from configuration — the pattern the "Get the code" section uses.
Treat the Connected Services dependency as a convenience that may need a Visual Studio repair or update on the affected install, not as a requirement — nothing in your project depends on the wizard having succeeded. ## Practice exercise

Try it yourself (10 minutes, code in the description):

Run SqlConnectCheck against LocalDB — it prints your server version and three demo rows.

In SQL Server Object Explorer, run a New Query against the same instance: CREATE DATABASE PracticeDb; — then change ONE word in the connection string (the database name) and re-run. PracticeDb starts empty, so watch what the checker does: it creates the DemoCustomers table inside it, seeds the same three rows, prints them back, and ends with the same success line.

Now break it on purpose: mistype the instance name, re-run, and read the error like a detective — which of the post's six errors is it? Reply with the @@version line your run printed — I read every one.

FAQ

Do I need SSMS if I have Visual Studio?
No — everything here works without it. Install SSMS when the job becomes administering the server itself: backups, jobs, logins, configuration.

Is SQL Server free for this?
Yes, for development and testing: the Developer editions and LocalDB cost nothing and need no key. Developer editions are not licensed for production — Express is the free edition that is.

Does this work on Visual Studio 2026? VS Code?
2026: yes — same three tools, same clicks. VS Code is a different editor with its own SQL extension; a different path, not covered here.

Get the code

The companion folder has the C# console checker (SqlConnectCheck, Microsoft.Data.SqlClient 6.1.7 LTS, connection string from an environment variable), the Python/pyodbc version, setup.sql exactly as run above, and a README with the six errors in miniature:

https://github.com/sajjad037/visual-studio-learn-code/tree/main/topic-07-connect-sql-server-vs

Sources — the official Microsoft Learn pages behind this post

Every version pin and procedure above traces to Microsoft Learn (accessed November 3, 2026):

Visual Studio 2022 release notes (17.14.44): https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes
SSMS 22 release notes (22.11.3): https://learn.microsoft.com/en-us/ssms/release-notes-22
Microsoft.Data.SqlClient support lifecycle (6.1.7 LTS, supported to August 14, 2028): https://learn.microsoft.com/en-us/sql/connect/ado-net/sqlclient-driver-support-lifecycle?view=sql-server-ver16
Editions and supported features of SQL Server 2025 (the Enterprise/Standard Developer split): https://learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2025?view=sql-server-ver17
SQL Server downloads (the free Developer editions): https://www.microsoft.com/en-us/sql-server/sql-server-downloads
Hardware and software requirements for installing SQL Server 2025: https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025?view=sql-server-ver17
SQL Server Express LocalDB (the automatic MSSQLLocalDB instance, and Microsoft's own LocalDB connection-string example): https://learn.microsoft.com/en-us/sql/connect/ado-net/sql/sqlclient-support-localdb?view=sql-server-ver17

Disclosure: Visual Studio Learn is reader-supported. Some links may be affiliate links, which means the channel may earn a small commission at no extra cost to you. Only tools actually used in the tutorials are ever linked, and affiliate relationships never change a verdict.

DEV Community: Visual Studio Learn