SQL Data Warehouse
Do you have an idea or suggestion based on your experience with SQL Data Warehouse? We would love to hear it! Please take a few minutes to submit your idea or vote up an idea submitted by another SQL Data Warehouse customer. All of the feedback you share in these forums will be monitored and reviewed by the SQL Data Warehouse engineering team. By suggesting or voting for ideas here, you will also be one of the first to know when we begin work on your feature requests and when we release the feature.
Remember that this site is only for feature suggestions and ideas! If you have technical questions please try our documentation, MSDN forum, or StackOverflow. If you need support, please open a support ticket with us.
-
107 votes
Dynamic Data Masking feature is now on our near-term plan. Thanks for your feedback.
-
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.
27 votesThanks for your suggestion. We are looking into this scenario for a future release. 6386782
-
Support EXECUTE AS for stored procedures
As part of the ELT procedure the user staging data should be able to call a transform procedure to ingest the data without having read/write permissions to the production tables.
22 votesThanks for your feedback. Azure SQL Data Warehouse Support for EXECUTE AS feature is now in progress.
-
default port
Configure SQL Data Warehouse to listen on a port that is different from the default 1433 port such as port 80 and/or port 443.
6 votes -
Hide schema objects based on role
We want to hide dbo and other custom schemas from users. We have stage, test, dbo, etc. objects in the DW. We would like to limit the schemas and/or objects that we expose to them through SQL Roles. We can limit their ability to query a certain schema, but I want to limit their ability to see it
5 votes -
Database auditing functionality in APS
Currently SQL DW and SQL Server allow one to audit database access. This functionality does not exist in APS. Please provide the ability to audit data access in APS as well.
4 votes -
Grantable Schema-level truncate permission
Need schema level TRUNCATE access so roles for ETL processes can be granted TRUNCATE in addition to INSERT/UPDATE/DELETE and said ETL processes don't have to own the table targeted for the TRUNCATE operation.
3 votes -
Support Security Option to grant non-admin user access to catalog views and DMVs
Support Security option to grant non-admin users access to catalog views and DMVs (without making them db_owner, effectively)
3 votes -
database level firewall
The following documentation states that a database level firewall works for Azure SQL DW databases:
https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-set-database-firewall-rule-azure-sql-databaseHowever, running the syntax mentioned results in the error:
Msg 15165, Level 16, State 1, Line 1
Could not find object 'sp_set_database_firewall_rule' or you do not have permission.Please add or fix support for the database-level firewall in Azure SQL DW
2 votesThanks for reporting this. We are looking into this. 10703354
-
Support ALTER AUTHORIZATION for all relevant object classes
Need to be able to change the ownership of any object in ADW that has an owner. For example a ROLE. Currently only DATABASE, SCHEMA, and OBJECT are suported.
2 votes -
Visual Stuido ADW connection shows Admin user name
Hi,
When you connect to azure dw or db using VS data tool, the connection windows displays database's admin login as default. can we change this not show the admin user name?thanks
1 vote -
SQL DW password policy profiles
We have multi-factor authentication (MFA) for AAD. Tableau and other tools connecting to data sources via ODBC cannot accommodate MFA. We can create local accounts in Azure SQL Server and SQL DW, but MUST CHANGE, CHECK EXPIRATION, and CHECK POLICY are not supported. We need to be able to enforce and report compliance with password security policies.
1 vote -
Create specific API REST operation for scaling instead of using the generic POST
Because the scaling operation is included in the generic write operation, if we need to configure a least privileges permission we would need to add the ability to create and update a database, which is way more than allowing just to scale a database.
1 vote
- Don't see your idea?