SQL Server Management Studio shows a folder for Database Scoped Credentials in case of an SQL Database but not in case of SQL Data Warehouse.1 vote
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.3 votes
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
Currently SQLDW doesn't have option to track deadlocks. It would be good if that option is available in Azure Portal as like SQL Database7 votes
Provide ActiveQueryCount as a result output under .properties for the REST API database state parameter.
I would absolutely magic if we had something like Snowflake:
- Automatically suspends the warehouse if no query has been issued during a fixed amount of time
- Automatically resumes the warehouse when a query is issued22 votes
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
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
The current workaround for cross subscription restore is:
- Restore to a new logical server in the same prod subscription
- ‘Move’ the new logical server with the restored data warehouse to new subscription
It would be faster and simpler to enable restore directly to a different subscription.72 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
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.213 votes
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.
The ability to restore a single table from backup, to an existing DW, would greatly assist in recovering from errors.59 votes
The current VNET endpoint solution does not allow connections via expressroute.
Allow a private IP from the VNET to be assigned to the data warehouse, so that we can easily route to the warehouse from on prem, via expressroute. Removing the need for any complex peering or other IT infrastructure involvement.9 votes
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.89 votes
Thank 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.
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
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 date5 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.
Create a simple columnstore table and look at sys.stats:
create table dbo.systemDefinedStatBug with (clustered columnstore index, distribution=round_robin)
select 1 as column1, 2 as column2;
from sys.stats s
where s.objectid = objectid('dbo.systemDefinedStatBug')
Notice it has a system generated "statistic". It use to be that row was marked as usercreated=0 so we could easily tell that's not a regular user created stat. But these days in SQL DW it says usercreated=1 on this "stat". Please fix this bug.5 votes
spsenddb_mail needs to be supported to send mails from stored procedures created on Azure.
We should have the abilities of spsenddbmail which was available with databases8 votes
Thank you for all the feedback folks. Please comment on your scenario below. You can create Azure alerts for metrics and logs along with Azure functions to send emails.
- Don't see your idea?