If the tens of millions of eventual readers of the book use Azure Data Studio for some of their work, that makes it easier to vote up PolyBase-related issues and feature requests. Azure Data Studio is a new product, so it’s easier to influence the product team. This is a little bit of a stretch, but not as much as you might think. But the idea is that PolyBase allows for data virtualization, meaning I don’t care where the data lives as long as it gets to me. In SSMS, all external tables show up in their own folder, hidden away from everything else. Built-in query editor, native Jupyter Notebooks, and an integrated. Its built for data professionals who use SQL Server and Azure databases on-premises or in multicloud environments. The Azure Data Studio team made a decision which I think is the right one: external tables are just tables. Designed to focus on the functionality data platform developers use the most, Azure Data Studio offers additional experiences available as optional extensions. If you are primarily focused on PolyBase, there’s nothing in that list which pushes me to say that you absolutely need SSMS. SQL Server Management Studio does have some PolyBase-related functionality: you can see external tables in their own folder you can right-click and get templates for new external data sources, file formats, and tables and you can see the members of your PolyBase Scale-Out Group.
#Execution plan azure data studio mac#
The ability for me to give a native Linux or Mac user a useful platform helps with bringing them into the fold. And on many of those platforms, Windows is a second-class citizen. One of the main use cases for PolyBase is to integrate with all kinds of data sources, including Hadoop, Oracle, Teradata, and the like.
Those timings, however, might well show up. A screenshot I guarantee you’ll never see in the book. Because I don’t plan to go into much detail on why in the book (after all, the book is about PolyBase, not SQL Server clients), I wanted to take a little time and walk through some of my reasoning for this.
As I work on PolyBase Revealed, I made a conscious decision to prefer Azure Data Studio for my demos over SQL Server Management Studio.
0 kommentar(er)
