I first introduced you to Azure Data Studio when the public preview for it was announced in December 2017. At the time, the name of the product was SQL Operations Studio, and its feature set was small and aimed squarely at the developer persona. It hadn't been long since the release of Microsoft SQL Server 2017, which ushered in an entire new audience and market for SQL Server due to the scale-out of availability to Linux after nearly 25 years of exclusivity to the Windows ecosystem. The push to Linux was ambitious, and it was critical for Microsoft to provide a gateway for the audience that didn’t frequently interact with Microsoft products--particularly Windows. SQL Operations Studio developed from that need.
Azure Data Studio continues to be a cross-platform solution that comes in three flavors: Windows, Linux and Mac OS. The platform's features have evolved rapidly, and the plan is for it to be eventually on par with the established-yet-aging SQL Server Management Studio.
According to Vicky Harp, Principal Program Manager Lead, for SQL Server tooling:
“Azure Data Studio shares a heritage and a roadmap with SQL Server Management Studio, which has been a phenomenally successful and well-liked tool in its own right. Over the course of time, all of the management features of SQL Server Management Studio will be made available in Azure Data Studio and the two products will integrate smoothly with each other. At present, Azure Data Studio is tightly focused on the experiences around query editing and data development. Additional high-value administrative features such as backup, restore, agent job management, and server profiling are also available as extensions in Azure Data Studio.”
Azure Data Studio has gone GA with a rich set of developer and DevOps-centric features. Microsoft will continue to release preview-class features as the platform evolves and receives new monthly updates through Microsoft’s commitment to continuous integration and delivery in its management tools for the data platform. Those preview-class features include:
- Flat file import
- SQL Server Agent
- SQL Profiler
- Azure Resource Explorer
- Graphical Query Show Plan
Based on this combination of features, one can draw the conclusion that Microsoft is now shifting toward closing the gap between Azure Data Studio and SQL Server Management Studio, making it a viable alternative for developers and DBAs alike. But the company has a long road in front of it. Currently, backup and restore functionality exists in Azure Data Studio as one of the sole DBA-focused features, which means SQL Server Management Studio (SSMS) is by far still the de-facto tool for SQL Server database administration (along with the Azure data portal for all Azure-based SQL experience administration). That does not mean that DBAs will not find interesting uses for Azure Data Studio, but for now the environment is ripe for use by those developing solutions for the Microsoft Data Platform, versus those administering instances of SQL Server on premises or administering one of the many Microsoft Azure offerings.
Getting Started with Azure Data Studio
Azure Data Studio has a very low learning curve. Here's what you need to know to get started.
1. Download and install the tool for the environment that suits your needs. (Windows, MacOS and Linux downloads are all facilitated from the same link, provided here.)
2. Connect to the instance of your choice. The process is quite similar for either Azure or on-prem environment connectivity, but there are some differences to note that may lead to frustration in connecting to Azure implementations:
For either cloud or “earthed” installs, enter the appropriate values for the following fields:
- Authentication Type (SQL login or Active Directory authentication)
- User name
In the case of an Azure connection, you’ll need to supply the server name in a fully-qualified format: <server_name>.database.windows.net. If this is the first time you’ve established a connection to the Azure instance, you’ll also need to configure firewall rules that will allow you access or you’ll need to work with an authorized individual in your organization who can configure the firewall settings appropriately for your situation. Azure Data Studio will provide you with the recommended IP address or address range to aid in the creation of the firewall rule. Firewall settings are accessed from the Azure Portal, not from within Azure Data Studio.
At this point, you’re connected. Based on your permissions, you can create, configure and develop solutions using SQL Server on premises or on one of the many Azure-based offerings: Azure SQL Database, Azure IAAS, Azure SQL Managed Instance, Azure SQL Data Warehouse, and SQL Server 2019 Big Data Clusters and Azure Data Studio Notebooks.
Stay engaged with IT Pro Today as we offer new, tips, tricks and training around Azure Data Studio and all the new offerings coming from Microsoft as it continues to evolve and scale its SQL and Azure offerings.