A common need is to expose a database through a configurable OData layer. Azure Synapse Analytics is just different enough from TSQL where traditional tools don't really work. Writing a simple app using Entity Framework doesn't even work with ASA as a few important keywords (like OFFSET) are unsupported.

Currently, creating an "if condition" activity means nesting the conditionally executed tasks inside the if-activity. This makes making changes to the control flow quite cumbersome, Preferable it would be possible to drag lines to to control the order of conditionally executed tasts. "If True" gets the green line and "If False" gets the red line. This is how we would white board it in a meeting, and it is more efficient, considering you can otherwise not re-use activities that are nested in a conditional.

We need to be able to cross reference executed queries in the database with issues such as DWU level, CPU, Maintenance Window... etc. For example if I execute a query to view historical queries, there is no valid comparison unless I show the level of the DWU as well at each particular time. If there were 200 executions, this would take a long time.

We need to be able to cross reference executed queries in the database with issues such as DWU level, CPU, Maintenance Window... etc. For example if I execute a query to view historical queries, there is no valid comparison unless I show the level of the DWU as well at each particular time. If there were 200 executions, this would take a long time.

Hi, looking for technologies that answer to high requirements in terms of security and analytics, and wondering if it would make sense to enable Azure Synapse Analytics on-premise ? We are seeing some trends of cloud solutions reverting to become hybrid. What about this solution ? Thanks.

As described here https://docs.microsoft.com/en-us/sql/t-sql/statements/create-external-file-format-transact-sql?view=azure-sqldw-latest, none of the default acceptable datetime formats supported in an External file have timezone support.
When DATE_FORMAT isn't specified or is the empty string, PolyBase uses the following default formats:
• DateTime: 'yyyy-MM-dd HH:mm:ss'
• SmallDateTime: 'yyyy-MM-dd HH:mm'
• Date: 'yyyy-MM-dd'
• DateTime2: 'yyyy-MM-dd HH:mm:ss'
• DateTimeOffset: 'yyyy-MM-dd HH:mm:ss'
• Time: 'HH:mm:ss'

Requirement:
Add at least one timeformat in list of default acceptable datetime formats so that datetimeoffset columns can be used along with other datetime types in a single external file.

Currently there is no way to know the version number of the datawarehouse by running either select @@version or SELECT SERVERPROPERTY('ProductVersion'). These will give you the same values such as "10.0.11115.0" even after multiple upgrades and are not useful for tracking purposes. Can you please add a functionality to that returns the proper version and build numbers? Also the release notes provides only feature enhancements but not bug fixes, if you can add bug fixes in the following location, that would be fantastic as well - https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/release-notes-10-0-10106-0

Add code formatting feature to the editor, similar to VS Code or Azure Data Studio.

Hi Team,

SQL DW and SQL DB should have password expiry option.
As of now password never expires. Please implement password expiry.
It is one of the compliance requirement in Philips.

SQL Server Management Studio shows a folder for Database Scoped Credentials in case of an SQL Database but not in case of SQL Data Warehouse.

I would like to be able to do full back ups more frequently than once a day.

We should have report on Azure portal which shows performance level of ADW or Azure Database with respect to time stamp and Cost incurred for that period.

With this report we should get cost incurred for a particular instance and duration the instance was in different performance level for a period.

This helps in financial planning for future depending upon the trend of cost incurred for that instance.

We should need a exception of fire wall rule that allows accessing from trusted Azure Service same as Storage Account.

How to extend the backup retention period to 35 days from 7 days for our SQL DW / MS product group team could you please help on this

Full and simple integration between azure Datalake and azure DW with the notebooks. Support for commom database connection drivers like pyodbc. And the most import, simple way to use Azure Active Directory log in to DW and Data Lake using Windows or Linux VM !

We would like to synapse to support also unloading data using copy into statement. This is supported in Snowflake and Redshift.
https://docs.snowflake.net/manuals/user-guide/data-unload-azure.html#unloading-data-directly-into-an-azure-container

Can you add Azure SQL Data Warehouse as one target and Azure SQL Database as one source in Microsoft Database Migration Assistant software?

It would be nice to be able to use T- SQL syntax such as OPENROWSET etc. in SSMS or Azure Data Studio to query Azure Data Lake Storage files.

External file formats with UTF-16 encoding are not obeying the USETYPEDEFAULT= FALSE logic and are converting NULL marks in flat files to USETYPEDEFAULT = TRUE logic. There appears to be some kind of implicit conversion to UTF-8 causing NULL marks to no longer correctly appear.