We’re announcing the upcoming retirement of Azure Data Studio (ADS) on February 6, 2025, as we focus on delivering a modern, streamlined SQL development experience. ADS will remain supported until February 28, 2026, giving developers ample time to transition.
This decision aligns with our commitment to simplifying SQL development by consolidating efforts on Visual Studio Code (VS Code) with the MSSQL extension, a powerful and versatile tool designed for modern developers.
Why Retire Azure Data Studio?
Azure Data Studio has been an essential tool for SQL developers, but evolving developer needs and the rise of more versatile platforms like Visual Studio Code have made it the right time to transition. Here’s why:
Focus on innovation
VS Code, widely adopted across the developer community, provides a robust platform for delivering advanced features like cutting-edge schema management and improved query execution.
Streamlined tools
Consolidating SQL development on VS Code eliminates duplication, reduces engineering maintenance overhead, and accelerates feature delivery, ensuring developers have access to the latest innovations.
Why Transition to Visual Studio Code?
VS Code is the #1 developer tool, trusted by millions worldwide. It is a modern, versatile platform that meets the evolving demands of SQL and application developers. By transitioning, you gain access to cutting-edge tools, seamless workflows, and an expansive ecosystem designed to enhance productivity and innovation. We’re committed to meeting developers where they are, providing a modern SQL development experience within VS Code. Here’s how:
Modern development environment
VS Code is a lightweight, extensible, and community-supported code editor trusted by millions of developers. It provides:
- Regular updates.
- An active extension marketplace.
- A seamless cross-platform experience for Windows, macOS, and Linux.
Comprehensive SQL features
With the the MSSQL extension in VS Code, you can:
- Execute queries faster with filtering, sorting, and export options for JSON, Excel, and CSV.
- Manage schemas visually with Table Designer, Object Explorer, and support for keys, indexes, and constraints.
- Connect to SQL Server, Azure SQL (all offerings), and SQL database in Fabric using an improved Connection Dialog.
- Streamline development with scripting, object modifications, and a unified SQL experience.
- Optimize performance with an enhanced Query Results Pane and execution plans.
- Integrate with DevOps and CI/CD pipelines using SQL Database Projects.
Streamlined workflow
VS Code supports cloud-native development, real-time collaboration, and thousands of extensions to enhance your workflows.
Transitioning to Visual Studio Code: What You Need to Know
We understand that transitioning tools can raise concerns, but moving from Azure Data Studio (ADS) to Visual Studio Code (VS Code) with the MSSQL extension is designed to be straightforward and hassle-free. Here’s why you can feel confident about this transition:
No loss of functionality
If you use ADS to connect to Azure SQL databases, SQL Server, or SQL database in Fabric, you’ll find that the MSSQL extension supports these scenarios seamlessly. Your database projects, queries, and scripts created in ADS are fully compatible with VS Code and can be opened without additional migration steps.
Familiar features, enhanced experience
VS Code provides advanced tools like improved query execution, modern schema management, and CI/CD integration. Additionally, alternative tools and extensions are available to replace ADS capabilities like SQL Server Agent and Schema Compare.
Cross-platform and extensible
Like ADS, VS Code runs on Windows, macOS, and Linux, ensuring a consistent experience across operating systems. Its extensibility allows you to adapt it to your workflow with thousands of extensions.
If you have further questions or need detailed guidance, visit the ADS Retirement page. The page includes step-by-step instructions, recommended alternatives, and additional resources.
Continued Support
With the Azure Data Studio retirement, we’re committed to supporting you during this transition:
- Documentation: Find detailed guides, tutorials, and FAQs on the ADS Retirement page.
- Community Support: Engage with the active Visual Studio Code community for tips and solutions. You can also explore forums like Stack Overflow.
- GitHub Issues: If you encounter any issues, submit a request or report bugs on the MSSQL extension’s GitHub repository.
- Microsoft Support: For critical issues, reach out to Microsoft Support directly through your account.
Transitioning to VS Code opens the door to a more modern and versatile SQL development experience. We encourage you to explore the new possibilities and start your journey today!
Conclusion
Azure Data Studio has served the SQL community well,but the Azure Data Studio retirement marks an opportunity to embrace the modern capabilities of Visual Studio Code. Transitioning now ensures you’re equipped with cutting-edge tools and a future-ready platform to enhance your SQL development experience.
For a detailed guide on ADS retirement , visit aka.ms/ads-retirement.
To get started with the MSSQL extension, check out the official documentation.
We’re excited to see what you build with VS Code!
This a complete miss and mess. If ADS is going to transition over to VS Code, then it needs to fully transition. The current extension provided is hot garbage at best. There are tons of features that are missing in the #no-loss-of-functionality extension. SSMS is the same heavy install/ARACHIC interface. Please do better. Super annoying. Might as will slap in a fabric interface to go along with it.
Does Microsoft plan to support SQL Server Management Studio (SSMS) on Linux given that Azure Data Studio (ADS) has been slated for deprecation?
At present, SSMS is not supported on Linux and as such there would be a functionality gap for Linux users for SQL Server Agent and Profiler as per the plan posted at this link:
https://learn.microsoft.com/en-us/azure-data-studio/whats-happening-azure-data-studio
Is the link for MSSQL extension “official documentation” being a redirect to Bing deliberate?
Very disappointed to lose such a discreet and well functioning app for such a messy alternative. I use VS code extensively, and switching to ADS was a deliberate act of using a streamlined, and well configured, IDE.
I would also note the lack of export or import of existing connections and groups does not qualify the existence of any sort of “migration” path.
This is so stupid. Once I found out about ADS I started using it and love it. It is my daily driver for sql work, and I'm furious that you're killing it for a vscode plugin that doesn't have feature parity.
ADS is great because it's lightweight. It loads fast and doesn't hog resources the way SSMS does. And this is very important when your on a work laptop with limited resources and need to have several instances of visual studio open at a time.
Best of all, it is a STANDALONE sql client. I don't want to use vscode for this...
I just tried the VS Code extension, and the first thing I noticed is that there isn’t any option to import my connections from ADS. Am I going to have to manually recreate all my connections? If you’re going to retire a perfectly good tool and redirect us to a lesser alternative, the least you could do was provide an easy migration path. Really disappointing.
It’s already open-source: https://github.com/microsoft/azuredatastudio
It is really a shame. While I didn’t use it for MS SQL, I used it extensively with PostgreSQL. I’d love to have seen it gain more database drivers for things like SQLite, Oracle, Snowflake, DB/2 and so on. Being a specialized database tool allows it to push a more narrow API for extensions that is useful in making sure UI is uniform and consistent between different databases. I don’t expect the same consistency to be maintained moving to VS Code, which is a too with a different goal.
Is there a SQL Profiler extension for VS, to replace the SQL Profiler extension available in Azure Data Studio?
Repeating some of the other comments (and it's possible/likely I missed some things, I've only played around for a few minutes):
- I liked having a separate app to keep software dev and db work separate
- Colored tabs
- F5 to execute a query (is this already a setting somewhere?)
- Buttons to save results as csv or xlsx
- ADS was easier to change the database, but I'll probably get used to that
- Can the font of the results be changed? I like the look of ADS better than what's in Code.
- The filter dialog on...
Looks like the buttons to save as csv and Excel are there and I missed them earlier. And I changed the execute command to F5, though it’s possible that will goof me up when working on a C# project with .sql files?
Nick, I went searching for this the other day – you can adjust the SQL Results font here:
File > Preferences > Settings > Extensions > MSSQL configuration > Results Font Family (Microsoft Sans Serif) and Results Font Size = 11.
You can’t colour null results as yellow like ADS or SSMS as far I can see, but I find the font change much easier on the eyes.
Darn, I was really enjoying watching Azure Data Studio make all that great progress on SSMS feature completeness… Guess it’s back to square one.
Also, I’d seriously question the “Hey lets throw everything we can into VS Code as a plugin” mentality.
I understand the move, but I kinda liked having a separate app for database work. I guess I can just have a separate VS workspace…
I also liked having a separate app. Setting up a VS Profile gets close, but it still runs under the same VS Code app. In light of this news, I submitted this GitHub issue to request having profiles show as separate apps to the OS (macOS Dock or Windows Taskbar), but it was just closed as “not planned” without any discussion. https://github.com/microsoft/vscode/issues/239960
As others have said, there’s a few key features in ADS that I use frequently:
– Schema Compare
– Servers Groups in connections dialogue, with coloured tabs option
– Graphical preview and interactivity on Security options (Users, Roles)
– SQL Server Dacpac extension
It would be great to get some visibility on whether these can/will be ported to VSCode.