Azure Synapse Analytics

We would love to hear your ideas for new features for Azure Synapse Analytics. Below, enter a new idea or upvote an existing one. The Synapse engineering team pays attention to all requests.

If instead you need a technical question answered or help, try the these options: DocumentationMSDN forum, and StackOverflow. If you need support, please open a support ticket.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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  ·  SQL/Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add support of JSON format

    Please add support of JSON data format like just happened for SQL Server 2016 and Azure SQL Database with JSONVALUE, JSONQUERY, 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  ·  SQL/Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow NVARCHAR(MAX) for variables.

    Storing dynamic SQL in NVARCHAR(4000) is not enough for our use case.

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

    We’ll send you updates on this idea

    0 comments  ·  SQL/Table Structure  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the suggestion. We have completed the first version of this feature and it has been rolled out worldwide. The following data types are now supported, NVARCHAR, VARCHAR, VARBINARY and BINARY. There are a couple of limitations in this first version. (1) PolyBase loads to these new data types will not be supported. But you will be able to load this data through other means like bcp. (2) Cluster ColumnStore tables do no yet support these data types. These data types are supported in Heap and Cluter Index Tables. 1028371

  4. Allow Unique Index on Columns that intersect the distribution column

    If SET tables aren't available, at least allow an UNIQUE INDEX to be placed on a table if the DISTRIBUTION column is found in the columns of the UNIQUE INDEX

    For example

    Table with locationid and productid with any number of fact columns. Partition the table by productid. All the data for any productid will be on one specific distribution. Allow that distribution to enforce uniqueness on locationid + productid.

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

    We’ll send you updates on this idea

    3 comments  ·  SQL/Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  5. sort a columnstore on CTAS/rebuild

    Columnstores can eliminate segments based on the min/max vaules of a column.

    For best performance, the data would need to be sorted by the users desired column, such as a date.

    See - http://www.nikoport.com/2014/04/16/clustered-columnstore-indexes-part-29-data-loading-for-better-segment-elimination/

    I'd love to see a syntax that looks something like the below (but without the need for creating a clustered index first)

    with
    (

    DISTRIBUTION = hash ( [store] ),
    
    clustered columnstore index (order by DateStamp)

    )

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

    We’ll send you updates on this idea

    1 comment  ·  SQL/Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  6. More Collation support + ability to set via the Portal

    Right now according to the documentation the only options for collation on SQL Data Warehouse are "The default collation is SQLLatin1GeneralCP1CIAS. The other collation option is Latin1General100CIASKS_WS."

    We run Latin1GeneralCI_AS which I suspect a large amount of UK customers would do. This is a supported Collation as per SQL Azure which we are migrating our operational datastore to but we can't move our data warehouse because of this. Also like SQL Azure can we have this as an option via the management portal when we create a DW.

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

    We’ll send you updates on this idea

    0 comments  ·  SQL/Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  7. Unable to see objects in object explorer

    We are unable to see list of objects using SSMS (any version). This would be require to navigate through database objects.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL/Table Structure  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base