Quick verdict
Use VS Code with the MSSQL extension if you came from Azure Data Studio for querying, notebooks, schema compare or SQL projects, or if you work on macOS or Linux: Microsoft names it as the replacement, and it can import your Azure Data Studio connections, connection groups and settings. Use SSMS 22 on Windows for SQL Server Agent jobs, security management, Always Encrypted, performance dashboards and other administration, which Microsoft says stays in SSMS. Most SQL Server teams will need both: VS Code for development, SSMS for administration.
Why this comparison now. Microsoft's page on Azure Data Studio states that it "is retired as of February 28, 2026 and no longer receives updates or security fixes" and tells users to migrate to Visual Studio Code with the MSSQL extension. The last Azure Data Studio release was 1.52, dated 18 June 2025. For the retirement itself and what happens to an existing installation, see SSMS vs Azure Data Studio and our Azure Data Studio page. This page answers the next question: of the two Microsoft tools left, which one should you open for which job.
SQL Server Management Studio (SSMS) is Microsoft's Windows application for configuring, managing and administering SQL Server, Azure SQL Database, Azure SQL Managed Instance and SQL database in Fabric. The current release is SSMS 22.10.2 (28 September 2026). It is free, built on Visual Studio 2026 and runs on 64-bit Windows, including Arm64. See our SSMS review.
Visual Studio Code with the MSSQL extension is a free extension for Microsoft's cross-platform editor. Microsoft lists Object Explorer, a query plan visualiser, table and schema designers, schema compare, SQL notebooks, Query Profiler, backup and restore, DACPAC and BACPAC import and export, flat-file import and GitHub Copilot integration as generally available, on Windows, macOS and Linux. See our VS Code MSSQL extension review.
Side by side
| Aspect | SSMS | VS Code (MSSQL extension) |
|---|---|---|
| Platforms | Windows only (Windows 11 and Windows Server 2019 to 2025, 64-bit, including Arm64) | Windows 10 and 11, macOS (Intel and Apple silicon), Linux (x64 and Arm64) |
| Microsoft's positioning | Supported home for SQL Server Agent and full administration | Named replacement for Azure Data Studio for daily development work |
| Azure Data Studio import | No import of Azure Data Studio connections documented | Azure Data Studio Migration imports connections, connection groups, settings and key bindings |
| Notebooks | No notebook feature documented | SQL notebooks in the native Jupyter .ipynb format with an MSSQL kernel |
| Execution plans | Estimated and actual plans, live query statistics, Query Store reports | Estimated and actual plans in the query plan visualiser |
| Tracing and Extended Events | XEvent Profiler (live Extended Events viewer); legacy SQL Server Profiler is deprecated | Query Profiler built on Extended Events, with session templates, filters and CSV export |
| Schema compare and projects | Schema Compare and the Database DevOps workload generally available since 22.10.2 | Schema Compare (databases, .dacpac files, SQL projects); SQL Database Projects extension |
| Extensions | Microsoft components through the Visual Studio Installer; third-party extensions not supported | Full VS Code extension marketplace (Git, Jupyter, PostgreSQL and others) |
| Engines | Microsoft SQL engines, plus SSIS, SSAS and SSRS administration | SQL Server, Azure SQL and SQL database in Fabric; other engines through separate extensions |
| Main trade-off | Deepest administration tooling, but Windows only and closed to third-party extensions | Cross-platform and extensible, but not a full administration console (no SQL Server Agent management) |
Key differences
Feature map: where each Azure Data Studio habit goes
Based on Microsoft's replacement tables and the documentation for each feature, this is where the things people did in Azure Data Studio now live:
- Saved connections and server groups: the MSSQL extension's Azure Data Studio Migration feature imports saved connections and connection groups (groups keep their names and colours, connections keep server, database and authentication metadata) and supported settings. In SSMS, Registered Servers is the equivalent for organising servers, but Microsoft does not document an import from Azure Data Studio, so you recreate them.
- Key bindings: the MSSQL Database Management Keymap companion extension restores Azure Data Studio shortcuts in VS Code (F5 to run, Ctrl+L for the estimated plan, Ctrl+M to toggle the actual plan). Microsoft notes it does not carry over your own custom key bindings.
- Notebooks: SQL notebooks in the MSSQL extension use the native VS Code Jupyter format (
.ipynb), connect to a SQL Server instance and can switch databases on that server; install the Jupyter extension to use a Python kernel. SSMS has no notebook feature, so notebooks belong in VS Code. - Extensions: VS Code uses its own marketplace, so Git, Jupyter and the PostgreSQL extension are a click away. SSMS delivers extra features as Microsoft workloads (for example SSIS, SSAS and GitHub Copilot) and does not support third-party extensions.
- Query plans: both show estimated and actual execution plans. The MSSQL extension's visualiser highlights expensive operators by metrics such as cost and actual elapsed time and can save the plan or open its XML. SSMS adds live query statistics, client statistics and Query Store reports.
- Profiler and Extended Events: Microsoft maps the Azure Data Studio Profiler extension to Query Profiler in VS Code and XEvent Profiler in SSMS. Both are built on Extended Events; SQL Trace and SQL Server Profiler are deprecated.
- Schema compare and SQL projects: Schema Compare exists in both tools. In VS Code it compares databases,
.dacpacfiles and SQL projects and can apply changes or generate a script; SSMS 22.10.2 made its Schema Compare and the Database DevOps workload (SQL projects) generally available. - SQL Server Agent and administration: SSMS. Microsoft's guidance is to use SSMS "for SQL Server Agent and full administration"; the MSSQL extension covers common database operations (create, rename, drop, back up, restore, search).
Administration: why SSMS stays
Microsoft's SSMS FAQ says to use SSMS for complex administrative or platform configuration, security management (logins, users, roles and Always Encrypted), performance tuning advisors and dashboards, database diagrams and table designers, Registered Servers, and live query or client statistics. None of these is listed as an MSSQL extension feature, and Microsoft's Azure Data Studio guidance sends SQL Server Agent work to SSMS.
SSMS also administers SQL Server Integration Services, Analysis Services and Reporting Services, and SSMS 22.10.2 brought GitHub Copilot Agent Mode, the SQL Formatter and Schema Compare to general availability. The limits are platform and openness: Microsoft states that SSMS "is available only for Windows", is not open source and does not support third-party extensions.
Development: why VS Code is the default for former Azure Data Studio users
VS Code keeps what made Azure Data Studio popular: the same editor model, a marketplace, built-in Git and the ability to run on macOS and Linux. The MSSQL extension adds the SQL tools on top, and Microsoft says existing queries, scripts and SQL database projects open in VS Code without conversion. It also includes features Azure Data Studio users relied on extensions for, such as Query Profiler, database backup and restore, and DACPAC and BACPAC import and export.
The trade-off is scope. Microsoft's retirement page says VS Code with the MSSQL extension primarily supports SQL Server, Azure SQL Database, Azure SQL Managed Instance and SQL database in Fabric, and that SQL Server Agent and full administration belong in SSMS. For PostgreSQL alongside SQL Server, add Microsoft's PostgreSQL extension; Microsoft lists the MySQL replacement as pending announcement.
Migration steps from Azure Data Studio
- Install VS Code and the MSSQL extension on every machine that ran Azure Data Studio; on Windows administration machines, install SSMS 22 as well.
- Run Azure Data Studio Migration from the VS Code Command Palette, point it at your Azure Data Studio settings file, and choose the connection groups, connections and settings to import.
- Install the keymap if you want Azure Data Studio shortcuts, then re-create any custom key bindings by hand.
- Open notebooks in VS Code, select the MSSQL kernel (or install the Jupyter extension for Python cells) and re-run them before you rely on the output.
- Move Agent jobs and administration to SSMS, and replace Profiler sessions with Query Profiler or XEvent Profiler.
- Re-point schema compare and deployment to the MSSQL extension, SSMS 22 Schema Compare or SqlPackage in pipelines.
- Uninstall Azure Data Studio, because it receives no security fixes.
Pricing and licensing
SSMS. Free. Microsoft's FAQ states that SSMS is free for personal or enterprise use, has its own licence agreement and needs no Visual Studio subscription.
VS Code with the MSSQL extension. Free to download and install from Microsoft and the Visual Studio Code Marketplace.
Pricing checked on the vendors' official pages on 8 October 2026. Prices change; confirm before buying.
Where each one leads
SSMS strengths
- Microsoft's supported home for SQL Server Agent and full administration
- Security management, Always Encrypted, performance dashboards and Registered Servers
- Live query statistics, client statistics and Query Store reports alongside execution plans
- Schema Compare, SQL projects (Database DevOps) and SQL Formatter generally available in 22.10.2
- Administers SSIS, SSAS and SSRS as well as the Database Engine
VS Code (MSSQL extension) strengths
- Runs on Windows, macOS and Linux, including Arm64
- Imports Azure Data Studio connections, connection groups, settings and key bindings
- SQL notebooks in the native Jupyter .ipynb format
- Query Profiler on Extended Events, schema compare, DACPAC and BACPAC, backup and restore
- Full extension marketplace, built-in Git, and extensions for other engines such as PostgreSQL
Limitations
SSMS limitations
- Windows only; Microsoft states it does not run on macOS
- Third-party extensions are not supported, and SSMS is not open source
- No notebook feature
- Works with Microsoft SQL engines only
VS Code (MSSQL extension) limitations
- No SQL Server Agent job management; Microsoft points full administration to SSMS
- Primarily supports SQL Server, Azure SQL and SQL database in Fabric; other engines need other extensions
- No Microsoft MySQL replacement yet (listed as pending announcement)
- Custom Azure Data Studio key bindings are not imported and must be set again
When to choose each
Choose SSMS if
- You manage SQL Server Agent jobs, logins, roles or Always Encrypted
- You tune with live query statistics, Query Store reports or performance dashboards
- You administer SSIS, SSAS or SSRS
- You work on Windows and want one tool for administration and querying
Choose VS Code (MSSQL extension) if
- You are moving from Azure Data Studio and want your connections and shortcuts back
- You use SQL notebooks or want queries, notebooks and Git in one editor
- You work on macOS or Linux
- You also work with PostgreSQL or other languages in the same window
When neither is right
- You want one desktop client for SQL Server, PostgreSQL, MySQL and more: see DBeaver vs SSMS and DataGrip vs VS Code.
- You want a wider shortlist: see the best SSMS alternatives and the best SQL Server GUI tools.
- You mainly need MySQL tooling, for which Microsoft has not announced an Azure Data Studio replacement: see the best MySQL GUI tools.
Final recommendation
For former Azure Data Studio users the default move is VS Code with the MSSQL extension: it runs everywhere Azure Data Studio did, imports your connections and settings, and covers notebooks, query plans, profiling and schema compare. Keep SSMS 22 on Windows for SQL Server Agent, security and the rest of administration, where Microsoft still directs you. Install both if you do both kinds of work, and uninstall Azure Data Studio once the move is done.
Frequently asked questions
When was Azure Data Studio retired?
On 28 February 2026. Microsoft states it no longer receives updates, security patches or maintenance, and recommends Visual Studio Code with the MSSQL extension. The last release was 1.52 on 18 June 2025.
Can I import my Azure Data Studio connections into VS Code?
Yes. The MSSQL extension's Azure Data Studio Migration feature imports saved connections, connection groups and supported settings from your Azure Data Studio settings file, and can install a keymap with Azure Data Studio shortcuts. Custom key bindings are not included.
Does SSMS support notebooks?
No notebook feature is documented for SSMS 22. Use SQL notebooks in the MSSQL extension for VS Code, which use the standard Jupyter .ipynb format.
What replaces SQL Server Profiler?
Extended Events. Microsoft marks SQL Trace and SQL Server Profiler as deprecated and points to XEvent Profiler in SSMS and Query Profiler in the MSSQL extension for VS Code.
Can VS Code manage SQL Server Agent jobs?
The MSSQL extension does not list SQL Server Agent management. Microsoft's guidance is to use SSMS for SQL Server Agent and full administration.
Is there SSMS for Mac?
No. Microsoft states that SSMS is available only for Windows. On macOS, use VS Code with the MSSQL extension.
Sources
- Microsoft Learn: What's happening with Azure Data Studio
- Microsoft Learn: Azure Data Studio release notes
- Microsoft Learn: MSSQL extension for Visual Studio Code
- Microsoft Learn: Transition from Azure Data Studio (MSSQL extension)
- Microsoft Learn: SQL Notebooks (MSSQL extension)
- Microsoft Learn: Query Profiler (MSSQL extension)
- Microsoft Learn: Schema Compare (MSSQL extension)
- Microsoft Learn: SSMS FAQ
- Microsoft Learn: SSMS 22 release notes
- Microsoft Learn: SSMS system requirements
- Microsoft Learn: Use the SSMS XEvent Profiler
- Microsoft Learn: SQL Server Profiler
Checked October 2026.
How we research comparisons: our editorial method.