20 Use Cases for Microsoft Azure Data Studio and Current Workflows

Quick Answer

• Microsoft Azure Data Studio provided a cross-platform environment for: 
  • Database management and development
  • Serving database administrators
  • Developers
  • Data analysts 
• It supported SQL querying, data visualization, Jupyter Notebooks, source control, performance monitoring, database projects, and Azure integration.
• The platform supported various database workflows, from management, backup, and security to Kubernetes support, dashboard creation, and team collaboration. 
• Microsoft has retired Azure Data Studio and recommends Visual Studio Code with the MSSQL extension for many of its workflows, while SQL Server Management Studio remains the better choice for broader SQL Server administration. 

Microsoft Azure Data Studio was widely used for database administration, SQL development, and data analysis across different operating systems. It brought together tools for querying databases, visualizing data, monitoring performance, and managing database projects in a single interface. 

Microsoft has retired Azure Data Studio, and it is no longer receiving updates. The Azure Data Studio retirement means users should now consider supported tools for their database development and management workflows. Microsoft recommends Visual Studio Code with the MSSQL extension as the replacement. This article covers the key use cases and capabilities associated with Azure Data Studio while helping readers understand the current Microsoft-recommended Azure Data Studio alternative. 

What Was Azure Data Studio?

Microsoft Azure Data Studio was a cross-platform database management environment that helped data professionals

• Manage databases
• Write and execute SQL queries
• Analyze data
• Monitor database performance

It combined database management capabilities with development and visualization features in a modern interface.

The tool also supported features such as source control, database projects, extensions, custom dashboards, and integrations with Azure data management services, making it useful across a range of database development and administration tasks.

Is Azure Data Studio Still Supported?

As mentioned earlier, Microsoft has retired Azure Data Studio, and the tool no longer receives updates or support. Users should transition to a supported Microsoft development environment for ongoing database management and development.

What Should You Use Instead of Azure Data Studio?

Microsoft recommends Visual Studio Code with the MSSQL extension as the replacement for Azure Data Studio. This Azure Data Studio replacement supports SQL Server connections, T-SQL query development and execution, database management, and SQL Server data operations in a modern development environment.

Red River Tip: The best replacement may not be a single tool. Organizations should map their existing Azure Data Studio workflows to Visual Studio Code, the MSSQL extension, SSMS, or other specialized tools based on their specific requirements. 

20 Azure Data Studio Use Cases and Current Workflows 

Azure Data Studio was used for various database management and development workflows, which users can now perform through Visual Studio Code with the MSSQL extension or SQL Server Management Studio. 

1. Database Management

Azure Data Studio was used to create, modify, and manage databases and database objects. Today, these workflows can be handled through Visual Studio Code with the MSSQL extension, which provides Object Explorer and tools for creating, renaming, and dropping databases. For broader SQL Server administration, SQL Server Management Studio may be more appropriate.

Practical example: A developer can connect to SQL Server in Visual Studio Code, browse tables and stored procedures, and make routine database changes without leaving the editor.

2. SQL Querying and Execution

Azure Data Studio provided a SQL editor with features such as IntelliSense, code completion, and query execution. The MSSQL extension for Visual Studio Code provides a similar current workflow, including IntelliSense, T-SQL execution, query results, and execution-plan viewing.

Migration tip: Existing .sql scripts can be opened directly in Visual Studio Code without conversion.

3. Data Visualization

Azure Data Studio supported extensions for turning query results into interactive visualizations. Azure data visualization can help transform database query results into clear, actionable insights. Today, users should evaluate Visual Studio Code extensions and dedicated data visualization tools based on the type of analysis required.

Limitation: Visual Studio Code does not necessarily reproduce every Azure Data Studio visualization extension feature, so teams should review their existing workflows before migrating them.

4. SQL Notebooks and Data Analysis

Azure Data Studio was commonly used for notebook-based SQL analysis. The current MSSQL extension supports SQL Notebooks in Visual Studio Code, allowing users to combine executable T-SQL cells with Markdown documentation.

Limitation: A SQL Notebook currently connects to one SQL Server instance at a time, although users can switch databases on that server.

5. Extensions and Customization

Azure Data Studio offered an Extensions Marketplace for adding functionality. After retirement, users should look for equivalent Visual Studio Code extensions, particularly the MSSQL extension and SQL Database Projects extension.

Migration tip: Do not assume every Azure Data Studio extension has a direct replacement. Review extensions individually and identify supported alternatives before moving production workflows.

6. Source Control

Azure Data Studio supported Git-based source control for database scripts and other development artifacts. Visual Studio Code provides built-in source-control integration with Git, making it the natural replacement for version-controlled SQL development.

Practical example: Teams can store T-SQL scripts and SQL database projects in a Git repository, review changes, create branches, and integrate database changes into existing development workflows.

7. Performance Monitoring

Azure Data Studio included tools for investigating query performance and execution plans. The MSSQL extension now provides query execution plans and performance-related tooling within Visual Studio Code.

Alternative: For deeper SQL Server monitoring and administration, organizations may need SSMS or dedicated monitoring solutions.

8. Data Import and Export

Azure Data Studio could import and export data in common formats. The MSSQL extension provides current database operations, including importing flat files such as CSV and TXT files.

Limitation: More complex ETL and data integration requirements may call for dedicated Azure or SQL Server data tools rather than an editor extension.

9. Backup and Restore

Azure Data Studio supported database backup and restore operations. This workflow can now be performed through the MSSQL extension for Visual Studio Code, which supports full, differential, and transaction-log backups as well as restoring from backup sets, files, or Azure Blob Storage.

Alternative: SSMS remains an option for administrators who need a broader SQL Server administration interface.

10. Server Management

Azure Data Studio allowed users to connect to and work with multiple SQL Server instances. The MSSQL extension provides connection profiles, Object Explorer, database object management, and query execution in Visual Studio Code.

For comprehensive server administration, however, SSMS is generally the better choice than treating Visual Studio Code as a complete replacement for every DBA workflow.

11. Azure SQL Integration

Azure Data Studio was used to connect to Azure SQL services. The MSSQL extension continues this workflow by supporting Azure SQL Database, Azure SQL Managed Instance, SQL Server on Azure Virtual Machines, SQL Server, and SQL Database in Microsoft Fabric.

12. Job Scheduling

Azure Data Studio could be used to work with SQL Server Agent jobs. After retirement, organizations that need to create, configure, schedule, and monitor SQL Server Agent jobs should use SQL Server Management Studio or appropriate SQL Server administration tools.

Migration guidance: Keep scheduled database maintenance and automation workflows in established SQL Server administration environments rather than assuming all SQL Server Agent functionality has moved to the MSSQL extension.

13. Database Projects

Azure Data Studio supported database projects for organizing schemas and deploying database changes. The current SQL Database Projects extension for Visual Studio Code provides a supported workflow for creating, editing, building, and publishing SQL database projects. Existing .sqlproj projects can be opened in Visual Studio Code without conversion.

14. Schema Comparison

Azure Data Studio supported schema comparison workflows. Users migrating to Visual Studio Code can use the schema comparison capabilities available through the MSSQL ecosystem to identify differences between database schemas and prepare changes.

Practical example: Developers can compare development and target database schemas before publishing a database project.

15. Data Profiling

Azure Data Studio could be extended for data profiling and quality analysis. Today, teams should evaluate Visual Studio Code extensions or dedicated data-quality and analytics tools depending on their profiling requirements.

Limitation: There may not be a direct Visual Studio Code equivalent for every data-profiling extension previously available in Azure Data Studio, so teams should evaluate their existing workflows before migrating.

16. Custom Dashboards

Azure Data Studio allowed users to create dashboards displaying database and server metrics. After retirement, dashboard requirements should be matched to the appropriate tool, such as SSMS, Azure monitoring services, or dedicated database monitoring platforms.

Visual Studio Code is better positioned as a development and database-workflow environment than as a comprehensive replacement for every monitoring dashboard.

17. Cross-Platform Database Development

Azure Data Studio was popular partly because it ran across Windows, macOS, and Linux. The MSSQL extension for Visual Studio Code supports database development across Windows, macOS, and Linux. 

This makes Visual Studio Code a practical replacement for teams that previously relied on Azure Data Studio for cross-platform SQL development.

18. Kubernetes and Cloud-Native SQL Workloads

Azure Data Studio enabled users to work with SQL Server deployments hosted on Kubernetes. Users can now use the MSSQL extension in Visual Studio Code to connect to supported SQL Server environments, while Kubernetes-specific tasks should be managed through dedicated Kubernetes and cloud-native platforms.

Limitation: Visual Studio Code is not a full replacement for dedicated Kubernetes management platforms.

19. Security and Access Management

Azure Data Studio provided interfaces for working with database users, roles, and permissions. The MSSQL extension can support routine database development and object management, but complex security administration should be handled through SQL Server’s established administrative tools and organizational security processes.

Practical example: A developer might use Visual Studio Code to inspect database objects and run approved permission scripts, while a DBA manages broader access policies through SSMS.

20. Collaboration and Development Workflows

Azure Data Studio supported collaborative development through features such as notebooks, source control, and shared development workflows. Visual Studio Code now provides a broader development ecosystem around Git, SQL projects, notebooks, and collaboration tools.

Migration tip: Move SQL scripts and projects into Git-based workflows and use Visual Studio Code as the primary development environment, while retaining SSMS for administration-heavy tasks.

Azure Data Studio Migration

With Azure Data Studio retired, Microsoft recommends moving database development workflows to Visual Studio Code with the MSSQL extension. The extension supports many of the SQL Server development and management workflows previously handled through Azure Data Studio, including database connections, T-SQL querying, database object management, and SQL database projects.

For a smoother transition, the MSSQL extension includes migration capabilities that can help move supported Azure Data Studio settings and configurations into Visual Studio Code. Existing SQL scripts and database projects can be opened directly in Visual Studio Code during the migration process.

For detailed migration steps and supported features, see Microsoft’s Azure Data Studio transition and migration documentation.

Red River Tip: Before migrating from Azure Data Studio, review your existing queries, database projects, extensions, and administrative workflows. This helps determine which tasks should move to Visual Studio Code with the MSSQL extension and which are better suited to SSMS. 

Red River’s Support for More Streamlined Database Management

As organizations transition from Azure Data Studio to Visual Studio Code with the MSSQL extension, Red River can help modernize and streamline their database management workflows. Red River provides cloud, IT, cybersecurity, and technology services that can support organizations with database environments, infrastructure modernization, security, and ongoing management.

Red River can help organizations evaluate their current database workflows, identify opportunities for modernization, and align database development and management with their broader IT environment. This can include supporting cloud migration, infrastructure modernization, security, automation, and database-related operational processes.

For organizations managing SQL Server and Azure environments, Red River can also help connect database modernization efforts with broader cloud and IT strategies, helping teams improve efficiency while maintaining security and operational requirements.

Contact us to find out more.

Q&A