Azure Synapse is an analytics service that brings together data warehousing and Big Data analytics. Azure Synapse brings these two worlds together with a unified experience to ingest, prepare, manage, and serve data for BI and machine learning needs. For more information, see, What is Azure Synapse Analytics.
Azure Synapse is Azure SQL Data Warehouse evolved. We've taken the same industry-leading data warehouse to a whole new level of performance and capabilities. You can continue running your existing data warehouse workloads in production with dedicated SQL pool (formerly SQL DW) in Azure Synapse. For more information, see What is Azure Synapse Analytics.
Dedicated SQL pool refers to the standalone platform of enterprise data warehousing features that are generally available with Azure Synapse. For more information, see What is Azure Synapse Analytics.
What is the difference between dedicated SQL pools (SQL DW) and dedicated SQL pools in Azure Synapse workspaces?
Not all features of the dedicated SQL pool in Azure Synapse workspaces apply to a standalone dedicated SQL pool (formerly SQL DW), and vice versa. For more information, see What's the difference between Azure Synapse dedicated SQL pools (formerly SQL DW) and dedicated SQL pools in an Azure Synapse Analytics workspace?.
You can get started with an Azure trial account.
Azure Synapse offers several solutions for protecting data such as TDE and auditing. For more information, see Security.
Visit the Azure Compliance page for various compliance offerings by product such as SOC and ISO.
Yes! Though Power BI supports direct query with Azure Synapse, it's not intended for a large number of users or real-time data. To optimize Power BI performance further, consider using Power BI on top of Azure Analysis Services or Analysis Service IaaS.
See our current capacity limits page.
Several factors can influence the time for compute management operations. A common case for long running operations is transactional rollback. When a scale or pause operation is initiated, all incoming sessions are blocked and queries are drained. In order to leave the system in a stable state, transactions must be rolled back before an operation can commence. The greater the number and larger the log size of transactions, the longer the operation will be stalled restoring the system to a stable state.
See data types.
Many features are supported. Features that aren't supported can be found in Unsupported Table Features.
Yes. Most REST functionality that can be used with SQL Database is also available with dedicated SQL pool (formerly SQL DW). You can find API information within REST documentation pages or Databases.
Driver support for dedicated SQL pool (formerly SQL DW) can be found on the Connection Strings page
Orc, RC, Parquet, and flat delimited text
No, PolyBase only interacts with the storage components.
HDI can use either ADLS or WASB as the HDFS layer. If you have either as your HDFS layer, you can load that data into a dedicated SQL pool (formerly SQL DW). However, you cannot generate pushdown computation to the HDI instance.
For more information on dedicated SQL pool (formerly SQL DW) in Azure Synapse, see our Overview page.