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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Cross Database Querying

    Enable elastic query for SQL DW - this would allow cross database query in SQL DataWarehouse.

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

    We’ll send you updates on this idea

    10 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

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

    We’ll send you updates on this idea

    13 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

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

    We’ll send you updates on this idea

    19 comments  ·  Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. ANSI joins support in UPDATE & DELETE statement

    SQL DW does not support to usual way of joins (ANSI) in UPDATE, DELETE statement. This makes difficult in case of table data modification. Though there is a workaround provided for CTAS this seems to be a lengthy process of data modification. Please have this feature available in SQL DW.

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

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…

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

    We’ll send you updates on this idea

    8 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support for Recursive CTE

    It would be great if you can add support for recursive CTEs for computing hierarchical data

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

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support for spatial data type

    Spatial data shlould be supported by SQL Data Warehouse the same way it is supported by SQL Server.

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

    We’ll send you updates on this idea

    under review  ·  6 comments  ·  Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    96 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 →
  9. 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!

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

    We’ll send you updates on this idea

    10 comments  ·  Management  ·  Flag idea as inappropriate…  ·  Admin →

    Thank 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.

  10. Provide File Format to read 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.

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

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

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

    We’ll send you updates on this idea

    2 comments  ·  Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Rename a column name in SQLDW

    Scenario: We want to change the column name as it is changed in the source. And in table where we are trying to do has more than 20Billion records.
    Workaround: Since rename of column is not possible currently in SQL DW we are doing CTAS of that big table.
    Issues With Work around: It is very slow because we can’t do CTAS on entire big table in single transaction because of transaction limits and we end up doing in CTAS and with multiple insert statements . Which is very time consuming process
    ASK: Please support column Rename

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

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
  13. @@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(row_count) AS row_count
    FROM sys.dm_pdw_sql_requests
    WHERE row_count <> -1
    AND request_id IN
    ( SELECT TOP 1 request_id
    FROM sys.dm_pdw_exec_requests
    WHERE…

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

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
  14. More flexible date formats in Polybase

    Polybase currently has very limited date format support. All of the acceptable date formats have dashes or slashes. For example, I can't define a date format of yyyyMMdd since it doesn't have slashes or dashes. Please allow any date format I can express.

    Also, please allow more than one date format per external table. For example, what if I have a date column as yyyyMMdd and then a different column as yyyyMMddHHmm. With only being able to define one date format in the CREATE EXTERNAL FILE FORMAT statement I think I can't handle both formats.

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

    We’ll send you updates on this idea

    8 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  15. hash distribute fact table on multiple columns

    A large fact table often has multiple join keys to multiple dimension table, so while it can be opitmised for one join it always creates data movement for other joins. The hash distribution should accept multiple columns so all joins are optimised and create no data movement for dimension joins.

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

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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).

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

    We’ll send you updates on this idea

    under review  ·  4 comments  ·  Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  17. Inline and Table Valued Function support

    Currently Functions can only return a single variable, but we need to be able to return full tables so we can use them within the WHERE clause.

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

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
  18. 58 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
  19. Load a subset of data - currently you can either point to a source file or a source folder

    A few ways this can be done: defining a regular expression or wild card support

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

    We’ll send you updates on this idea

    2 comments  ·  Polybase  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

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

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base