There are two possible ways:
To use Polybase from SQL Server to access Azure tables and
Polybase from Azure tables to access SQL Server.
Option #2 It doesn’t really make under the Azure table architecture. Adding a Polybase layer into Azure tables would add extra overhead to the system and
wouldn’t add any value (since Azure tables don’t support complex queries, like joins, all work would need to be done on the client anyway, so why not just access the data directly from it’s original source.)
So let’s look at #1. That would mean the ability to use Azure tables with the T-SQL language and possibly within SQL queries, but is it supported?
Refer to this
documentation:
https://docs.microsoft.com/en-us/sql/relational-databases/polybase/polybase-guide, gives the overview:
PolyBase is a technology that accesses data outside of the database via the t-sql language. In SQL Server 2016, it allows you to run queries on external data in
Hadoop or to import/export data from Azure Blob Storage. Queries are optimized to push computation to Hadoop. In Azure SQL Data Warehouse, you can import/export data from Azure Blob Storage and Azure Data Lake Store.
Azure tables aren’t in the list, but certainly seems like a logical idea for inclusion.
Another possibility is using Azure Data Lake to indirectly access the data; however, it doesn’t appear that’s supported either, although it appears to be under
discussion:
https://feedback.azure.com/forums/327234-data-lake/suggestions/12264009-query-windows-azure-storage-table-in-azure-data-la
------------------------------------------------------------------------------------------
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members
