Please add support of JSON data format like just happened for SQL Server 2016 and Azure SQL Database with JSON_VALUE, JSON_QUERY, etc.75 votes
Thanks for your suggestion. We are looking into this scenario for a future release. 6386751
Spatial data shlould be supported by SQL Data Warehouse the same way it is supported by SQL Server.75 votes
Thanks for the suggestion. We are looking into this scenario for a future release. 6386746
It would be great if you can add support for recursive CTEs for computing hierarchical data73 votes
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.65 votes
Thanks for the suggestion. We are looking into this scenario for a future release. 7633476, 7633478
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).44 votes
Thanks for your suggestion. We are looking into this scenario for a future release. 10697276
XML datatype is not supported in ADW now.17 votes
Thanks for your suggestion. We are looking into this scenario for a future release. 10698276
Add the ability to store table extended properties so that meta data about the table can be stored. This will help with self documentation to aid BI Developers.16 votes
Thanks for your suggestion. We are looking into this scenario for a future release. 7350424
Currently, there is no support for user defined types which is making it difficult for us to migrate code from Azure SQL to Azure SQL DWH.9 votes
Thank you for your request. We have added this item to our backlog. We will update this thread when the state changes.
Table Trigger are very helpful f.e. auditing DML-code execution.3 votes
Allow the DDL to be specified once for a temporary table and then let applications instantiate an instance of the table in their sessions when the object is referenced (with an INSERT statement) if not already created in the session.3 votes
Thank you for your request. This item is on our backlog. We will update this item when the state changes.
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
Table with location_id and product_id with any number of fact columns. Partition the table by product_id. All the data for any product_id will be on one specific distribution. Allow that distribution to enforce uniqueness on location_id + product_id.3 votes
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.
I'd love to see a syntax that looks something like the below (but without the need for creating a clustered index first)
DISTRIBUTION = hash ( [store] ),
clustered columnstore index (order by DateStamp)
My best candidate distribution key is 40% nulls.
At present, distributing on this value will result in one overloaded distribution, where all the nulls will land.
As nulls will never join to any other table, it would suit this use case to have equal distribution of null rows across all distributions, so that the non-null foreign keys can benefit from being distribution aligned.
I understand this would be a change in behaviour, so perhaps a new distribution option could be created i.e. HASH_AND_NULL(my_foreign_key)1 vote
Support clustered column store indexes on large objects like varchar(max)/nvarchar(max)1 vote
Need to support ANSI INTERVAL data types in CREATE TABLE so applications can be ported from other data warehouse offerings.1 vote
Allow table to be created as SET and not only MULTISET.1 vote
- Don't see your idea?