Thank you for all the feedback folks. Unfortunately this is taking longer than we’d like. We will reach back out when it is on the roadmap and can share when we have an update.
Have you seen the new Query Store feature? This enables many of the scenarios around query retention.
Thank you for voting for this feature! We are aware of this scenario and are looking into ways of supporting this. In the meantime, stay tuned for an update and please continue voting for this feature.
Hi there. Depending on the size of the table and your workload, if your best candidate has so many nulls, you may be better off maintaining a round-robin distribution.
This functionality is supported. If this does not address your scenario, please comment below:
Hi Madhu, please do let us know if this article helps you: https://docs.microsoft.com/en-us/azure/sql-data-warehouse/manage-compute-with-azure-functions
This scenario is currently supported. Currently you can externally query SQL DW instances from SQL Database. Can you be more specific about the issue here?
Thanks for your suggestion. We are looking into this scenario for a future release. 10703657
Created due to the completion of IDENTITY. See here: https://feedback.azure.com/forums/307516/suggestions/12303591
Thank you for your feedback folks. We are actively looking into this scenario specifically with VS SSDT Database Project support with SQL Data Warehouse. Please continue voting and monitoring this item for updates. Thank you for your patience.
Hey Alex - Can you elaborate on what debugger you are using? As a separate note, we now support NVARCHAR(MAX) within SQL Data Warehouse.