The LABEL column in the sys.dmpdwexec_requests DMV is limited to 255 characters.
This field needs to be much larger to store rich metadata/context of some queries.4 votes
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.
It does not seem possible to change the default language to anything other than English US. I would like to be ale to change the language to British. I have tried at user and db level and neither seem to be supported.
EXEC sp_configure 'default language', 23 ;
ALTER LOGIN [...] WITH DEFAULT_LANGUAGE=[British];4 votes
Primary and Secondary maintenance must be mutually exclusive (either Saturday / Sunday or during weekdays); We run batch jobs daily, with the exception of Saturday. Must schedule maintainance on Saturday.3 votes
Implement the sys.dmdbstatsproperties DMV to expose the modctr to get a better idea of when stats should be updated. using stats_date isn't a complete solution. as you have no idea if any rows have changed since that date3 votes
Thank you for all the feedback folks. We are continuously improving the manageability experience with SQL Data Warehouse which includes automatic statistics. We will reach back out when this is on the roadmap and can share when we have an update.
Persist Data dictionary to a separate database by allowing the customer to persist the DMV, which can be used by DBA for fixing performance issues3 votes
Thank you for voting for this feature folks. We’d like additional information before commenting on this topic. Please provide your scenario in the comments below. We currently have Query Data Store on our roadmap.
Allow proper due diligence to be done in introducing DDL change. Some object usage is not evident in the SQL text due to semantic layers, generated SQL, etc.3 votes
Thank you for all the feedback. We are continuously improving the monitoring experience with SQL Data Warehouse. We will reach back out when this capability is on the roadmap and can share when we have an update.
Especially in dev environments, a currently running dw with no active queries is a waste. Some guard rails to protect users from themselves would be useful.
Something like the feature in databricks.2 votes
Ideally all billable components of a Data Warehouse should be visible via the Azure Portal.
We had a client recently who was trying to reconcile their billing, and could not do so as the DW size did not appear in the portal. This then required the DBA team to retrieve the size via the client admin tools: https://docs.microsoft.com/en-us/sql/relational-databases/databases/display-data-and-log-space-information-for-a-database?view=sql-server-2017
Trending on billable metrics potentially also helps customers forecast their upcoming Azure costs.2 votes
Allow install of Linux ODBC to be automated via puppet. The current Microsoft SQL Server ODBC packages can't be installed via puppet as they require EULA acknowledgment. If we adopted the ADW technology, we would inevitably have to install the ODBC software on several grids of computers that host our various ETL software. Puppet installation allows the implementers of new systems to get the software automatically installed without the DBA team's intervention.2 votes
Thank you for the feedback. Please follow up on this request with our tooling and drivers team as well. We will reach out when this is on our road map.
How to extend the backup retention period to 35 days from 7 days for our SQL DW / MS product group team could you please help on this1 vote
SSDT Visual Table editor is disabled with Synapse. Please add support for this feature. This is one of the reasons to use SSDT over SSMS for development.1 vote
To be able to export a Restore Point to Blob Storage to meet Compliance data retention policy's, and be able to restore a warehouse from the blob data set. We are on legal hold and not allow to delete backups at this time and the only way to meet this requirement is to export the each table to blob.1 vote
Provide ActiveQueryCount as a result output under .properties for the REST API database state parameter.
A resume operation and a scale operation appear to return about a minute too soon. If your automated code immediately attempts to connect to the DW as soon as the Azure CLI resume or scale operation completes you often get the error "Cannot connect to database when it is paused". A simple one minute pause usually prevents this but I would like resume or scaling operations to not return before we can actually connect to the DW.1 vote
Need to be able to cancel a query running from sqlcmd (on Linux) without terminating the session as KILL 'SIDxxxxx' does1 vote
Need to be able to specify a space quota for a schema and abort current work that causes the quota to be exceeded.
Forces user groups to be good stewards and manage their storage usage or be prevented from additional work.1 vote
Thank you for providing for this feedback folks. We’d like additional information before commenting on this topic. Please provide your scenario in the comments below specifically which quota configuration at the schema level.
- Don't see your idea?