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.

How can we improve Microsoft Azure SQL Data Warehouse ?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Replicated Table Support

    The feature is similar to that of redshift's Distribution style all. This will reduce data transfer between distributions/nodes and consequently improve performance.

    204 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  2. PolyBase: allow skipping header rows in delimited text files

    Setting reject rows in Polybase to ignore the header row is a hack. And if you have all string columns your header won't be rejected. Please add an IGNORE_HEADER_ROWS = <numRows> option to Polybase

    175 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add IDENTITY Types

    The fact IDENTITIES and SEQUENCE Types are missing makes it very difficult to generate surrogate keys. It seems the only pattern available is to combine ROW_NUMBER() with a select max from table, which is horribly clunky and won't work if parallel treads are loading into the table.

    160 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  4. Row-Level Security

    It would be great to implement Row-Level Security on SQL Data Warehouse.
    That would be a great solution for scenarios where (for example) we have clients like PowerBI using data from SQL warehouse, and persons who have limited data access.

    159 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  5. PolyBase: support for Azure Data Lake Store

    Polybase should add support for Azure Data Lake. I'm hopeful that will give us an option to do Polybase on top of files which are encrypted at rest.

    143 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add support of JSON format

    Please add support of JSON data format like just happened for SQL Server 2016 and Azure SQL Database with JSON_VALUE, JSON_QUERY, etc.

    133 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  7. PolyBase: allow retrieving rejected rows in an error file

    Let's say you define an external table with:

    REJECT_VALUE = 1000,
    REJECT_TYPE = value

    That means that it can reject and discard 1000 rows without failing the entire command.

    Please enhance Polybase to give us visibility into which rows were rejected and why. I would propose you can define an error output file where rejected rows get written. Either that or let us query some DMV to get a copy of the complete row as a string and the error reason.

    112 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  8. SQL Data Warehouse endpoint in the Virtual Network

    Currently Azure DWH is only accessible using the host name of logical SQL Server and all traffic goes through public Internet.

    Would be great to have an endpoint with a reserved IP within the Virtual Network to ensure given logical SQL Server is seen as an internal resources within the corporate network.

    103 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  9. Use SELECT for setting variables (SELECT @MyVar = Col1, @MyVar1 = Col2 ...)

    Because we cannot do SELECT @MyVar = Col1, we are forced to utilize the same code to execute the exact same sql, to assign multiple variables.

    59 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support for the full length of T-SQL statements that are run in an Azure SQL Data Warehouse

    The customer I’m working with is asking if there’s a way to know the full length of T-SQL statements that are run in an Azure SQL Data Warehouse instance.
    They are using sys.dm_pdw_exec_requests, but it truncates the query text keeping 4000 bytes.

    34 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →

    We are excited to announce that we have implemented Query Store for Azure SQL Data Warehouse. Query Store enables storing the full query text and aggregated execution statistics for all queries for a period of 7 days. You can learn more about Query Store in our blog post:

    https://azure.microsoft.com/en-us/blog/automatic-performance-monitoring-in-azure-sql-data-warehouse-with-query-store/

    Matt Usher
    Principal Program Manager
    Azure SQL Data Warehouse team

  11. Authenticate from Azure AD

    Allow users to authenticate using Azure Active Directory in addition to SQL Server authentication.

    30 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add Split_part function to SQL DW

    Just enable what's already in SQL (STRING_SPLIT) - it's the closest I've found to Redshift SPLIT_PART.

    29 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. PolyBase: support for encrypted Azure Blob Storage (Storage Service Encryption)

    There is a requirement to never leave unencrypted data anywhere. Inbound data files are encrypted but will have to be decrypted before Polybase can read them. In order to satisfy this requirement, Polybase will have to have ability to read encrypted files.

    28 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →

    Starting April 2016, Azure Storage Service Encryption (SSE) for Azure Blob Storage is in Public Preview. With this feature, Azure Storage automatically encrypts your data prior to persisting to blob storage and decrypts prior to retrieval, providing encryption at rest. We have tested this feature and PolyBase supports reading/writing data to encryption-enabled Azure Blob Storage. To learn more about Azure Storage Service Encryption, refer to https://azure.microsoft.com/en-us/documentation/articles/storage-service-encryption/.

    Thanks again for sharing your feedback with us. 6891055

  14. Enable Integrity and Privacy options for hadoop.rpc.protection setting

    Enable Integrity and Privacy options for hadoop.rpc.protection setting.
    Currently it only connects to Cloudera when set to Authentication, this doesn't provide sufficient security for storing/processing sensitive data.

    MS Work Items: 9519053 and 10001755.

    25 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  15. Release Notes

    It would be very nice to have something like a page with Release Notes after every update to Azure DWH.

    Now you accidentally find out that something that did not work , works.

    24 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  16. Azure AD Universal Authentication Integration in Visual Studio

    Organizations with MFA requirements have to use AD Universal Authentication to log into Azure SQL DB/DW. This can be done through SSMS, but support for Visual Studio would unlock more users.

    20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  17. Specify Time Window for Service Maintenance

    Allow customers to define a window of time during the day where any internal maintenance should be performed in order to reduce impact to users during core business hours.

    We have seen that internal upgrade/migration processes in Azure Data Warehouse can sometimes have impact on running queries (ex. performance and connection issues). If we could specify a time where impact is less likely, then it would improve the overall experience and availability.

    19 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Reliability  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support OVER (ROWS ...) SQL Syntax

    Azure SQL DWH doesn't support ROWS UNBOUNDED PRECEDING and similar RANGE inside OVER clause. This is quite painful, because it's frequently used for querying data warehouse.

    16 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
  19. Polybase to treat NULL string as Null values and not text.

    When we have files generated by third party we have little control over the file format, in our case huge data files with lots of NULL value are causing us trouble.

    14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  20. varchar(max) with Polybase

    need support for varchar(max) with polybase

    14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →

    This is currently a feature we support. We’ve recently increased the row support size to 1MB now. Generally one should avoid unnecessarily specifying a column to be max width if not necessary for performance reasons as well.

← Previous 1 3
  • Don't see your idea?

SQL Data Warehouse

Feedback and Knowledge Base