Azure Synapse Analytics
-
User Defined Retention Periods for Restore Points
SQL DW doesn't have the capability to specify longer term retention capabilities as released for SQL DB recently. The workaround is to restore and pause. It would be great to have this capability for compliance and auditing requirements.
342 votesThank 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.
-
Support for Recursive CTE
It would be great if you can add support for recursive CTEs for computing hierarchical data
216 votes -
Allow DWU to scale without interruption
The scaling disrupts the current session, and it's often not allowable in the production. Instead, it should finish off the existing session (sqls), and scale after that. That way, the scaling up or down can be done without causing the production disruption.
206 votesThank 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.
-
Support for Entity Framework
Support for Entity Framework in Azure SQL Data Warehouse would allow for greater usability in general, but it would also allow for better support of other frameworks/protocols. Specifically, we have a need to serve our data through an OData feed, and Entity Framework's deferred execution would allow us to handle OData's Query Options in a much simpler way.
192 votesThank 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.
-
Support for spatial data type
Spatial data shlould be supported by SQL Data Warehouse the same way it is supported by SQL Server.
189 votes -
Expose File Properties as additional columns to load in SQL DW
It would be helpful if some of the properties of a BLOB file could be exposed in the external table such as: Last Modified, Filename, Size. It should be optional and could be defined in the EXTERNAL FILE FORMAT definition. Each Property should be appended to the end of the result set of an external table in the order given in the definition.
For instance, if we are loading a directory of several files we can read the filename and derive a new column. For example, we might have a directory with 20160504.csv and 20160505.csv and the contents of the…
160 votesThanks for your suggestion. We are looking into this scenario for a future release. 7633537
-
Lower scale points for Dev/Test environments
SQL Data Warehouse scale stepping should be much smaller (10 DWU or even 1 DWU), than 100 DWU!
Please fix that ASAP!
Thank you!157 votesThank you for all the feedback folks. We are currently evaluating options for lower click stops for SQL Data Warehouse. Please continue to vote and comment on your scenario below. Thank you for your patience.
-
@@ROWCOUNT Support
Please enable @@ROWCOUNT?
Furthermore considering that we cannot switch NOCOUNT on, then why should it be such a secret/coded mission to track the number of rows affected by the most recent snippet of code? The proposed work-around seems onerous and doesn't always work (for dynamic SQL) yet my query window still knows and always-prints the fact that it returned 15 rows to me, for example, so why can we not leverage this elementary information inside the selfsame query (?):
SELECT SUM(rowcount) AS rowcount
FROM sys.dmpdwsqlrequests
WHERE rowcount <> -1
AND requestid IN
(…142 votes -
Temporal Table support in AzureSQLDW
Is this on the roadmap? Currently they are not a thing in the Parallel DW:
https://msdn.microsoft.com/en-us/library/dn935015.aspx?f=255&MSPPError=-2147217396129 votesThanks for your suggestion. We are looking into this scenario for a future release. 10714515
-
Provide File Format to read and load JSON and XML data from Storage
Able to read the JSON and XML file as part of external system OR provide functionality like Extractor in Data Lake analytics so we can write our own Extractor to read respective data format.
119 votes -
116 votes
-
Enable Intellisense With SSMS
Intellisense is a very handy feature when using SSMS to write queries against Sql Server databases. It increases development time by reducing typographical errors.
It would be nice to have with Sql Data Warehouse.
99 votesThank you for all the feedback folks. Unfortunately full intellisense support for SSMS 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.
-
Shrinkdatabase command support
Shrinkdatabase command should to be supported even if TDE is on or off because extra cost is charged in case that the unallocated space is huge.
90 votesThank you for all the feedback folks. We understand the scenario and are actively working on improving this experience. We will reach back out when it is addressed and share when we have an update.
-
Table Extended Properties
Add the ability to store table extended properties so that meta data about the table can be stored. This will help with self documentation to aid BI Developers.
78 votesThanks for your suggestion. We are looking into this scenario for a future release. 7350424
-
Pause Resume Azure SQL Data Warehouse Using SQL Command
It would be great if we can have SQL command to Pause/Resume DB instance like how we do for Scale up/down (under Master DB). This will help us to manage the same from ADF and don't have to worry about trigger REST API or PowerShell
76 votesThank you for voting for this feature. We understand this scenario and will consider this in a future release. For now, please continue monitoring this item and have your team vote for this feature. Thank you for your patience.
-
Support Always encrypted in SQL Data warehouse
Always Encrypted makes the data to be only available to client side applications and not visible to Database administrators also. It makes the data to be more secure. It is especially needed in the case of Azure, where PII data is stored in cloud.
69 votesThanks for your suggestion. We are looking into this scenario for a future release. 6386782
-
Stuff.....For XML
Please provide support for STUFF......FOR XML so we can do complex concatenation using Azure Data Warehouse. Right now its kind of show stopper for us due to time taken by workarounds (while loop).
69 votes -
Add support for synonyms
CTAS to a new table is often a pattern that's used in DW for data processing workloads. Instead of RENAME OBJECT operations from old tables to the new ones using CTAS, it would be great if we can add synonym support to DW, so that switching to the new table is an atomic operation, and is reliable.
66 votes -
Add WAITFOR command to SQL Datawarehouse
The following wont compile on ADW
IF @count = 4
BEGIN
WAITFOR DELAY '00:30';
SET @count = 0;
ENDPlease allow WAITFOR command on ADW
63 votesThank you for the feedback. We are reviewing the request.
-
Support table variables
Prior to data analysis it is required to collect some initial info and store it in a table format. Creating and dropping a table or a temp table takes too much time (seconds) since it has to be distributed over multiple nodes. Having table variables would solve this performance issue.
63 votes
- Don't see your idea?