[From Technet] The March release of Azure Data Studio is now available

Were excited to announce the March release of Azure Data Studio (formerly known as SQL Operations Studio) is now available.

Download Azure Data Studioand review the Release notes to get started.

Please note: If youre currently using the preview version of SQL Operations Studio, and would like to retain your settings when upgrading to the latest version, follow these instructions. After downloading Azure Data Studio, say Yes to enabling preview features so that you can use extensions.

Azure Data Studio is a multi-database, cross-platform desktop environment for data professionals using the family of on-premises and cloud data platforms on Windows, MacOS, and Linux. To learn more, visit our GitHub.

Check out this video for a general overview of Azure Data Studio.

The key highlights for the March release include:

• Announcing the PostgreSQL extension for Azure Data Studio
• Announcing SQL Notebooks
• Adding the PowerShell extension
• Adding the SQL Server dacpac extension
• Adding the community extension Queryplan.show
• Updates to the SQL Server 2019 Preview extension
• Bug fixes

For the list of complete updates, refer to the Release notes.

PostgreSQL extension for Azure Data Studio

When Azure Data Studio was released, it was with the intent and vision of creating a unified experience and supporting users in their choice of platform and data provider. Today we’re happy to take an important step forward in that direction with the release of preview support for PostgreSQL in the product, adding both on-premises and Azure Database for PostgreSQL to its existing support for SQL Server, Azure SQL Database, Azure SQL Managed Instance, Azure SQL Data Warehouse, and SQL Server 2019 big data clusters.

As the communitys #1 most requested feature, we’re excited to bring the innovative features we’ve built in Azure Data Studio over the past year to the PostgreSQL community. With support for PostgreSQL, we can officially state that Azure Data Studio is a multi-database, cross-platform tool for managing data.

The PostgreSQL extension in Azure Data Studio empowers users with their database development. The Azure Data Studio extension for PostgreSQL is backed up with a Tools API service that provides data management and high performant query execution capabilities. Azure Data Studio also offers a modern, keyboard-focused PostgreSQL coding experience that makes your everyday tasks easier with built-in features such as:

• Multiple tab windows
• IntelliSense
• Keyword completion
• Code snippets
• Code navigation
• Source control integration (Git)

In addition, users can run on-demand SQL queries, view and save results as text, JSON, or Excel. You can also leverage an Edit data UI, organize your favorite database connections, and browse database objects in a familiar object browsing experience.

The extension marketplace for Azure Data Studio makes it easy for developers and partners to build and contribute back into the open source ecosystem. PostgreSQL for Azure Data Studio will be a Microsoft offered extension empowering PostgreSQL developers to not only use a modern tool for their database development but also enable them to contribute back into the ecosystem to build further experiences.

We’re making the PostgreSQL extension experience open source under the MIT license and will seamlessly allow users to connect to all PostgreSQL databases independently if they’re running on Azure (Azure Database for PostgreSQL) or on-premises. Microsoft is committed to providing a great PostgreSQL developer experience through Azure Data Studio and empowering every PostgreSQL developer in the world to enhance their database experience and build richer applications.

To learn more about the PostgreSQL extension, you can visit our extension documentation orvisit our extension GitHub repository to file issues or feature requests.

 

SQL Notebooks

With the excitement of PostgreSQL joining Azure Data Studio, we havent forgotten about our passionate SQL Server users.

Today we’re excited to offer the first public preview of SQL Notebooks. Notebooks are a combination of human-readable and executable documents that allow rich text, images, code, and result sets to easily be shared. This is a concept that is widely used in data science and we feel is well suited to SQL work. With a notebook, you can easily interleave written instructions, analysis, diagrams, and even animated GIFs using markdown, then add code cells with the SQL code to be executed.

Early users have described to us many use cases they envision for SQL Notebooks, including:

• Teaching Tools
• Runbooks
• Business reporting and presentations
• Troubleshooting
• Deployments
• Baselining

Were excited to learn what the community can do with them!

The SQL Notebook functionality is now built into the base of the Azure Data Studio product, requiring no additional extensions or downloads in order to connect to servers and execute and save SQL result sets. You can get started with SQL notebooks just like a regular query editor. If you would like to use any other language such as Python, R, or Scala, youll be prompted to install some additional dependencies on the first use.

Oh, and it also works for PostgreSQL!

To see a live demo of SQL Notebooks, check out Vicky Harp and Chris LaFrenieres demo at SQL Bits. (SQL Notebooks starts at 20:30).

To get started with SQL Notebooks, view our tutorial on our Microsoft docs. If you have ideas of what you would like to see in SQL Notebooks or submit bugs, please submit an issue on the Azure Data Studio GitHub repository.

PowerShell extension

The well-known PowerShell extension from Virtual Studio (VS) Code is now featured in the Azure Data Studio marketplace. This extension was specifically driven by the community and involved partnering with the PowerShell team to make this supported in Azure Data Studio.

Bringing in the PowerShell extension aligns with many of the automation scenarios that database administrators and developers use. With the integrated terminal in Azure Data Studio, this makes it even easier to integrate PowerShell experiences with your data.

To learn more about the PowerShell extension and to submit feature requests and issues, visit the PowerShell extension GitHub.

SQL Server dacpac extension

Thanks to the great feedback from the community, weve been actively improving the Data-Tier Application Wizard in Azure Data Studio. This feature was originally shipped with the SQL Server Import extension, but well now ship this feature as a separate extension. We did this because we plan to bring more features to make it easier to use dacpacs and bacpacs in Azure Data Studio. This extension will also be part of the Admin pack for SQL Server, which is an extension pack that allows you to quickly download many of the popular features from SQL Server Management Studio.

For those unfamiliar with the Data-Tier Application Wizard, features include:

• Deploying .dacpac to SQL Server instance
• Extracting SQL Server instance to a .dacpac
• Creating a database from .bacpac
• Exporting schema and data to .bacpac

If you have features you would like to see in this extension, please feel free to leave a comment on this issue or open a feature request on our GitHub Issues.

Community extension highlight: Queryplan.show

Were always looking to support community members who are interested in building extensions for Azure Data Studio and having their extension featured in our extension marketplace. If you are interested in building extensions, you can get started here.

This month, Phil Scott built the Queryplan.show extension for Azure Data Studio. This extension adds integration support to visualize query plans using the community extension Queryplan.show that Phil also created.

We asked Phil about his experience and he shared this:

The extension stems from some ideas I have had floating around on how to change how we view query plans. I was first getting into serious SQL Server work 20 years ago when I first saw the graphical execution plan, and I remember how excited I was that I could easily see the inner working of how SQL Server was running my plans. But the visualization really hasn’t changed all that much since then. A few coats of paint here and there but it really hasn’t rocked the boat. So, I created a website that gave me an opportunity to try out some different visualizations for the query plans. I’m able to take ideas like “what if the query plan had the data operations on the left hand of the chart instead of scattered about on the right hand side” or “how can I view all the costs of the operators on one chart without having to scroll all over the place.” In addition to visualizing the whole plan, I’ve been trying to create specific operation displays. This way I can show the fields that are important to an Inner Join differently than the way an Index Scan would be displayed.

While I was getting closer to having visualizations that I was happy with, I was far from happy with how to get your plans into the site. It required users to paste in the XML of the query plan or uploading a saved sqlplan file. I briefly looked into the extensibility of SSMS but I was quickly in over my head there. Looking at the extensibility of Azure Data Studio was another story. I was able to get the extension running thanks to the WebView component in about 4 hours. Now with a few clicks you can load up the visualization within Azure Data Studio right from your query plan. I’m looking forward to future releases where hopefully the visualization with show by default when running an Explain operation.

You can get this extension from our Azure Data Studio marketplace. To submit issues or feature requests, you can visit the GitHub repository.

Visual Studio Code Refresh from 1.26.1 to 1.30.2

As we build new features into Azure Data Studio, we periodically refresh Azure Data Studio with stable and mature VS Code releases. This allows Azure Data Studio users to get the latest UI features implemented in VS Code.

Here are the latest refresh updates from the July release (1.26.1) to the November release (1.30.2) of VS Code. This includes many UI updates and you can get the full release notes by going to the respective release pages from August-November 2018. Highlights include:

• New Settings editor UI to make it easier to modify Azure Data Studio settings.
• Multiline search improvements
• Better macOS support

We will continue to bring VS Code refreshes into Azure Data Studio. Let us know if there are feature gaps you feel are missing.

SQL Server 2019 Preview extension

Over the last few releases, weve been moving features from the SQL Server 2019 preview extension into the core Azure Data Studio tool such as Notebook support. Here is a summary of the features moved into the core tool and bug fixes made to the External Data wizards.

Changes in release 0.11

• Jupyter Notebook support, specifically support for the Python3 and Spark kernels, has been moved into Azure Data Studio. This extension is no longer required in order to use Notebooks.
• Multiple bug fixes in the External Data wizards:
  • Oracle type mappings have been updated to match changes shipped in SQL Server 2019 Community Technology Preview (CTP) 2.3.
  • Fixed an issue where new schemas typed into the table mapping controls were being lost.
  • Fixed an issue where checking a Database node in the table mappings did not result in all tables and views being checked.

Bug fixes and feedback

If you would like to help continuing to make Azure Data Studio a great product, please share any feedback or report issues through our Issues page. Our engineering team is regularly going through the untriaged issues and assigning issues into different monthly milestones so that you know we are working on it. Your votes on issues helps us prioritize.

Please see the full list of bug fixes for the March release to learn more.

Contact Us

If you have any feature requests or issues, please submit to our GitHub issues page. For any questions, feel free to comment below or tweet us.

The post The March release of Azure Data Studio is now available appeared first on SQL Server Blog.

from SQL Server Blog https://ift.tt/2umWzcx