Azure Data Studio retires on February 28, 2026. No more updates, no more security patches, no more support. Microsoft announced this a year ago and has been pointing everyone toward VS Code with the MSSQL extension ever since.
Sounds straightforward. Install VS Code, add an extension, and carry on. Yet it is not really that simple, and it depends a lot on how you used ADS.
Who Uses ADS
Microsoft built ADS for a specific audience: data professionals who spend most of their time editing and executing queries rather than doing deep server administration. It runs on Windows, macOS, and Linux — which made it the only Microsoft-built SQL tool for non-Windows users. SSMS has never run on anything but Windows.
In practice, ADS carved out a few loyal audiences: Mac and Linux developers who needed a native SQL tool, db project users wanting source control integration without full VS, notebook users who built runbooks and documentation in SQL + Markdown, and even people who just wanted something lighter than SSMS for day-to-day query work.
What Is Actually Happening
Microsoft is consolidating. ADS was always built on the VS Code codebase, so maintaining both products meant duplicating effort. Rather than continue that, they are putting everything into VS Code and its MSSQL extension, and letting ADS go.
SSMS is not going anywhere. If you are an SSMS-only DBA who never touched ADS, this changes almost nothing for you. Keep reading anyway — the MSSQL extension is worth knowing about.
If you relied on ADS for cross-platform work, notebooks, database projects, or because you preferred the lighter interface — this is your migration notice.
Where Everything Goes
| ADS Feature | Replacement | Status |
|---|---|---|
| Query Editor | VS Code + MSSQL extension | Ready |
| Object Explorer | VS Code + MSSQL extension | Ready |
| Database Projects | VS Code + MSSQL extension | Ready — opens without migration |
| Schema Compare | VS Code + MSSQL extension | GA August 2025 |
| Connections Import | VS Code + MSSQL extension | New — added Jan 28, 2026 |
| SQL Server Agent | SSMS | Ready |
| SQL Profiler | SSMS | Ready |
| Notebooks | Polyglot Notebooks (VS Code) | Different extension, not 1:1 |
| Flat-File Import | Bulk Insert / PowerShell | In development for MSSQL |
| DACPAC Import/Export | SqlPackage CLI | Ready |
Most of this is in good shape right now, but a year ago not so much. Microsoft has been filling them — Schema Compare landed in preview, the Migration Toolkit for importing connections shipped on January 28th, and Table Explorer/Edit Data is now enabled by default. Credit where it is due: they have really been working this one.
Still, the migration is not seamless.
What You Lose
SQL Server Agent and Profiler are SSMS-only. If you managed Agent jobs or ran traces from ADS, those features have no VS Code equivalent. SSMS is the answer, which means Windows-only for those tasks. Mac and Linux users who leaned on ADS for lightweight Agent management are out of luck.
Notebooks are not a clean swap. ADS notebooks migrate to Polyglot Notebooks in VS Code, but it's a different extension with a different runtime. If you had SQL + Markdown notebooks that you used for runbooks or incident response documentation, test them before February 28. Do not assume they'll just work.
Flat-file import is gone (for now). ADS had a nice wizard for importing CSVs and text files directly into SQL tables. The MSSQL extension does not have that yet. Your options are bulk insert, PowerShell - and patience.
The Migration Toolkit is brand new. The ADS connection import feature shipped on January 28, 2026 — exactly one month before retirement. Better late than never, but it has had approximately twelve days of real-world use. If you have dozens of saved connections, you'll want to test the import early and verify.
What You Gain
It is not all bad news.
VS Code is faster, lighter, and has a massive extension ecosystem. The MSSQL extension has improved significantly with GitHub Copilot integration, connection groups, local SQL Server containers, and a modern query results pane that is genuinely better than what ADS offered. Your database projects open in VS Code without any migration steps. Your .sql scripts work as-is, and you are back on a platform that Microsoft is still actively investing in.
Who Cares and Who Does Not
| If You Are... | Impact |
|---|---|
| SSMS-only DBA | Minimal. You were never in ADS to begin with. |
| ADS on Mac/Linux | Significant. Agent and Profiler now require a Windows box. |
| Database Projects user | Smooth. Projects open directly in VS Code. |
| Notebook user | Bumpy. Test your notebooks before the deadline. |
| PostgreSQL/Cosmos user | Straightforward. VS Code extensions exist for both. |
What To Do Before February 28
1. Install VS Code + MSSQL extension. Download VS Code, then install the MSSQL extension from the marketplace. Takes two minutes.
2. Import your connections. The MSSQL extension now includes the Azure Data Studio Migration Toolkit. Use it to pull in your saved connections and connection groups. Then verify they actually work.
3. Open your database projects. They should just open. If they do not, that is a problem you want to discover now, not on March 1st.
4. Test your notebooks. Install Polyglot Notebooks in VS Code, open your existing notebooks, and run them. Fix what breaks while you still have ADS as a fallback.
5. Accept that Agent and Profiler live in SSMS. If you need them, SSMS 22 is GA and fully supports SQL Server 2025. It is not going anywhere.
The Bottom Line
ADS was always a bit of an identity crisis — too lightweight for serious administration, too heavy for 'just a query editor,' and perpetually compared to SSMS without ever reaching parity. Microsoft tried. The community mostly shrugged. And now it is being folded back into the tool it was forked from in the first place.
The migration is doable. Most of it is painless. The edges that aren't are well-defined, and we know exactly where the replacements are for what we are losing. That is more than we get with most Microsoft deprecations.
Do not wait until February 27th.
More to Read
Microsoft: What's Happening to Azure Data Studio?
VS Code Marketplace: MSSQL Extension
MSSQL Extension Release Notes (includes Migration Toolkit)
Microsoft DevBlog: Azure Data Studio Retirement
No comments:
Post a Comment