Hi @Serverless SQL ,
As per conversation with internal teams it is not in the short term roadmap but they are still reviewing the feedbacks. If you have any additional suggestions/feedback I would recommend you to please log your feedback as per the guidance provided in this article: How to send ideas and suggestions to the Synapse team - Microsoft Tech Community
But here are few workarounds which you can try:
- Setup an Azure SQL Database serverless so you will not get charged for compute except when it runs and then setup elastic queries - Below is an example on how to set it up. Using Elastic Query to Support SQL Spatial in Azure SQL DW – Mr. Fox SQL (wordpress.com)
- A second option is to set Azure Cosmos Database Geospatial and GeoJSON location data in Azure Cosmos DB | Microsoft Learn – You can set opt-in for the free tier of cosmos db so you will not get charged for it (it supports up to 1000 RU) which is very good – After you do so you can simply use the synapse link to access the data Azure Synapse Link for Azure Cosmos DB, benefits, and when to use it | Microsoft Learn
- Geospatial big data performance tests with Cosmos DB and data enrichment with Azure Synapse Analytics | by Remko de Lange | Towards Data Science
- A third option is to create an external table in Azure SQL Database serverless and connect to synapse - Here is an example Azure SQL | Read Data Lake files using Synapse SQL external tables (microsoft.com)
- A fourth option is using Synapse Spark to read these tables analyze and store it back into ADLS gen2 which is all part of Synapse.
The most popular workarounds are #3 and #4.
Hope this info helps.
----------
- Please
accept an answer
andup-vote
if it helps. Original posters help the community find answers faster by identifying the correct answer. Here is how. - Want a reminder to come back and check responses? Here is how to subscribe to a notification.