Skip to content

Commit 67d3134

Browse files
authored
Merge branch 'MicrosoftDocs:main' into 250728-arc-sql-settings
2 parents c95e031 + 67ede29 commit 67d3134

File tree

57 files changed

+826
-529
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

57 files changed

+826
-529
lines changed

azure-sql/azure-sql-iaas-vs-paas-what-is-overview.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,6 +171,14 @@ For **SQL Server on Azure VMs**, Microsoft provides an availability SLA of 99.95
171171

172172
[!INCLUDE [sql-database-create-manage-portal](includes/sql-database-create-manage-portal.md)]
173173

174+
## SQL database in Microsoft Fabric
175+
176+
You can also create a [SQL database in Microsoft Fabric](/sql/sql-server/fabric-database/sql-database-in-fabric). A [SQL database in Microsoft Fabric is distinct from an Azure SQL Database](/fabric/database/sql/decision-guide) or a mirrored database from Azure SQL Database, and each use similar mirroring technology to replicate data into Microsoft Fabric's OneLake.
177+
178+
With [SQL database in Fabric](/fabric/database/sql/overview), your data is automatically accessible from other Fabric experiences. SQL database in Microsoft Fabric, which uses the same SQL Database Engine as Microsoft SQL Server and is similar to Azure SQL Database, inherits most of the Fabric mirroring capabilities from Azure SQL Database. Your SQL database in Fabric is automatically mirrored to OneLake and presented in a read-only, queryable format. You can use all the different services in Fabric, such as running analytics with Spark, executing notebooks, data engineering, visualizing through Power BI Reports, and more.
179+
180+
For more information, see [SQL database in Microsoft Fabric (Preview)](/sql/sql-server/fabric-database/sql-database-in-fabric).
181+
174182
## Related content
175183

176184
For overviews:

azure-sql/database/configure-max-degree-of-parallelism.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: "Configure the Max Degree of Parallelism (MAXDOP)"
33
titleSuffix: Azure SQL Database
4-
description: Learn about the max degree of parallelism (MAXDOP) in Azure SQL Database.
4+
description: Learn about the max degree of parallelism (MAXDOP) in Azure SQL Database and SQL database in Fabric.
55
author: WilliamDAssafMSFT
66
ms.author: wiassaf
77
ms.reviewer: mathoma
8-
ms.date: 06/13/2025
8+
ms.date: 07/28/2025
99
ms.service: azure-sql-database
1010
ms.subservice: performance
1111
ms.topic: concept-article
@@ -16,18 +16,18 @@ dev_langs:
1616
ms.devlang: tsql
1717
monikerRange: "=azuresql || =azuresql-db || =fabricsql"
1818
---
19-
# Configure the max degree of parallelism (MAXDOP) in Azure SQL Database
19+
# Configure the max degree of parallelism (MAXDOP) in Azure SQL Database and SQL database in Fabric
2020

2121
[!INCLUDE [appliesto-sqldb-fabricsqldb](../includes/appliesto-sqldb-fabricsqldb.md)]
2222

23-
This article describes the **max degree of parallelism (MAXDOP)** configuration setting in Azure SQL Database.
23+
This article describes the **max degree of parallelism (MAXDOP)** configuration setting in Azure SQL Database and SQL database in Fabric.
2424

2525
> [!NOTE]
26-
> **This content is focused on Azure SQL Database.** Azure SQL Database is based on the latest stable version of the Microsoft SQL Server database engine, so much of the content is similar though troubleshooting and configuration options differ. For more on MAXDOP in SQL Server, see [Configure the max degree of parallelism Server Configuration Option](/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option).
26+
> **This content is focused on Azure SQL Database and SQL database in Fabric.** Azure SQL Database is based on the latest stable version of the Microsoft SQL Server database engine, so much of the content is similar though troubleshooting and configuration options differ. For more on MAXDOP in SQL Server and Azure SQL Managed Instance, see [Configure the max degree of parallelism Server Configuration Option](/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option).
2727
2828
MAXDOP controls intra-query parallelism in the database engine. Higher MAXDOP values generally result in more parallel threads per query, and faster query execution.
2929

30-
In Azure SQL Database, the default MAXDOP setting for each new single database and elastic pool database is 8. This default prevents unnecessary resource utilization, while still allowing the database engine to execute queries faster using parallel threads. It is not typically necessary to further configure MAXDOP in Azure SQL Database workloads, though it might provide benefits as an advanced performance tuning exercise.
30+
In Azure SQL Database and SQL database in Fabric, the default MAXDOP setting for each new single database and elastic pool database is 8. This default prevents unnecessary resource utilization, while still allowing the database engine to execute queries faster using parallel threads. It is not typically necessary to further configure MAXDOP in Azure SQL Database workloads, though it might provide benefits as an advanced performance tuning exercise.
3131

3232
> [!Note]
3333
> In September 2020, based on years of telemetry in the Azure SQL Database service MAXDOP 8 was made the [default for new databases](https://techcommunity.microsoft.com/blog/azuresqlblog/changing-default-maxdop-in-azure-sql-database-and-azure-sql-managed-instance/1538528), as the optimal value for the widest variety of customer workloads. This default helped prevent performance problems due to excessive parallelism. Prior to that, the default setting for new databases was `MAXDOP 0`. MAXDOP was not automatically changed for existing databases created prior to September 2020.
@@ -51,11 +51,11 @@ monikerRange: "=azuresql || =azuresql-db || =fabricsql"
5151

5252
## Considerations
5353

54-
- In Azure SQL Database, you can change the default MAXDOP value:
54+
- In Azure SQL Database and SQL database in Fabric, you can change the default MAXDOP value:
5555
- At the query level, using the **MAXDOP** [query hint](/sql/t-sql/queries/hints-transact-sql-query).
5656
- At the database level, using the **MAXDOP** [database scoped configuration](/sql/t-sql/statements/alter-database-scoped-configuration-transact-sql).
5757

58-
- Long-standing SQL Server MAXDOP considerations and [recommendations](/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option#Guidelines) are applicable to Azure SQL Database.
58+
- Long-standing SQL Server MAXDOP considerations and [recommendations](/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option#Guidelines) are applicable to Azure SQL Database and SQL database in Fabric.
5959

6060
- Index operations that create or rebuild an index, or that drop a clustered index, can be resource intensive. You can override the database MAXDOP value for index operations by specifying the MAXDOP index option in the `CREATE INDEX` or `ALTER INDEX` statement. The MAXDOP value is applied to the statement at execution time and is not stored in the index metadata. For more information, see [Configure Parallel Index Operations](/sql/relational-databases/indexes/configure-parallel-index-operations).
6161

@@ -74,13 +74,13 @@ monikerRange: "=azuresql || =azuresql-db || =fabricsql"
7474
> [!Tip]
7575
> We recommend that customers avoid setting MAXDOP to 0 even if it does not appear to cause problems currently.
7676
77-
Excessive parallelism becomes most problematic when there are more concurrent requests than can be supported by the CPU and worker thread resources provided by the service objective. Avoid `MAXDOP 0` to reduce the risk of potential future problems due to excessive parallelism if a database is scaled up, or if future hardware configurations in Azure SQL Database provide more cores for the same database service objective.
77+
Excessive parallelism becomes most problematic when there are more concurrent requests than can be supported by the CPU and worker thread resources provided by the service objective. Avoid `MAXDOP 0` to reduce the risk of potential future problems due to excessive parallelism if a database is scaled up, or if future hardware configurations provide more cores for the same database service objective.
7878

7979
<a id="modifying-maxdop"></a>
8080

8181
### Modify MAXDOP
8282

83-
If you determine that a MAXDOP setting different from the default is optimal for your Azure SQL Database workload, you can use the `ALTER DATABASE SCOPED CONFIGURATION` T-SQL statement. For examples, see the [Examples using Transact-SQL](#examples) section below. To change MAXDOP to a non-default value for each new database you create, add this step to your database deployment process.
83+
If you determine that a MAXDOP setting different from the default is optimal for your workload, you can use the `ALTER DATABASE SCOPED CONFIGURATION` T-SQL statement. For examples, see the [Examples using Transact-SQL](#examples) section below. To change MAXDOP to a non-default value for each new database you create, add this step to your database deployment process.
8484

8585
If non-default MAXDOP benefits only a small subset of queries in the workload, you can override MAXDOP at the query level by adding the `OPTION (MAXDOP)` hint. For examples, see [Examples using Transact-SQL](#examples).
8686

@@ -98,7 +98,7 @@ monikerRange: "=azuresql || =azuresql-db || =fabricsql"
9898

9999
## Examples
100100

101-
These examples use the latest `AdventureWorksLT` sample database when the `SAMPLE` option is chosen for a new single database of Azure SQL Database.
101+
These examples use the latest `AdventureWorksLT` sample database when the `SAMPLE` option is chosen for a new single database.
102102

103103
### PowerShell
104104

@@ -150,7 +150,7 @@ $params = @{
150150

151151
### Transact-SQL
152152

153-
You can use the [Azure portal query editor for Azure SQL Database](query-editor.md), [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms), or [Azure Data Studio](/azure-data-studio/download-azure-data-studio) to execute T-SQL queries against your Azure SQL Database.
153+
You can use the [Azure portal query editor for Azure SQL Database](query-editor.md), [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms), the [mssql extension](https://aka.ms/mssql-marketplace) for [Visual Studio Code](https://code.visualstudio.com/docs), or the [SQL query editor in the Fabric portal](/fabric/database/sql/query-editor) to execute T-SQL queries.
154154

155155
1. Open a new query window.
156156

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
55
author: WilliamDAssafMSFT
66
ms.author: wiassaf
77
ms.reviewer: mathoma, randolphwest
8-
ms.date: 07/09/2025
8+
ms.date: 07/28/2025
99
ms.service: azure-sql-database
1010
ms.subservice: service-overview
1111
ms.topic: whats-new
@@ -55,16 +55,16 @@ The following table lists the features of Azure SQL Database that are currently
5555
| **Network Security Perimeter** | [Azure Network Security Perimeter](network-security-perimeter.md) allows organizations to define a logical network isolation boundary for PaaS resources (for example, Azure Storage and SQL Database) that are deployed outside your organization's virtual networks. It restricts public network access to PaaS resources outside of the perimeter, and access can be exempted by using explicit access rules for public inbound and outbound. |
5656
| **Query editor in the Azure portal** | The [query editor in the Azure portal](query-editor.md) allows you to run queries against your Azure SQL Database directly from a web browser. |
5757
| **Regular expression functions** | Regular expression (REGEX) functions return text based on values in a search pattern. [Regular expressions](/sql/relational-databases/regular-expressions/overview). |
58-
| **UNISTR (Transact-SQL)** | Azure SQL Database now supports the `UNISTR` T-SQL syntax for Unicode string literals. For more information, see [UNISTR (Transact-SQL)](/sql/t-sql/functions/unistr-transact-sql).|
5958
| **Vector data type and functions** | Working with vector data is now easier in Azure SQL Database with the introduction of a new [vector data type](/sql/t-sql/data-types/vector-data-type?view=azuresqldb-current&preserve-view=true) and [vector functions](/sql/t-sql/functions/vector-functions-transact-sql?view=azuresqldb-current&preserve-view=true). For more information, see [Intelligent applications with Azure SQL Database](ai-artificial-intelligence-intelligent-applications.md#vectors).|
60-
| **\|\| (String concatenation) and \|\|= (Compound assignment) syntax support** | Azure SQL Database now supports [\|\| (String concatenation)](/sql/t-sql/language-elements/string-concatenation-pipes-transact-sql?view=azuresqldb-current&preserve-view=true) and [\|\|= (Compound assignment)](/sql/t-sql/language-elements/compound-assignment-pipes-transact-sql?view=azuresqldb-current&preserve-view=true) Transact-SQL syntax.|
6159

6260
## General availability (GA)
6361

6462
The following table lists features of Azure SQL Database that have been made generally available (GA) within the last 12 months:
6563

6664
| Feature | GA Month | Details |
6765
| --- | --- | --- |
66+
| **UNISTR (Transact-SQL)** | July 2025 | Azure SQL Database now supports the `UNISTR` T-SQL syntax for Unicode string literals. For more information, see [UNISTR (Transact-SQL)](/sql/t-sql/functions/unistr-transact-sql).|
67+
| **\|\| (String concatenation) and \|\|= (Compound assignment) syntax support** | July 2025 | Azure SQL Database now supports [\|\| (String concatenation)](/sql/t-sql/language-elements/string-concatenation-pipes-transact-sql?view=azuresqldb-current&preserve-view=true) and [\|\|= (Compound assignment)](/sql/t-sql/language-elements/compound-assignment-pipes-transact-sql?view=azuresqldb-current&preserve-view=true) Transact-SQL syntax.|
6868
| **Degrees of Parallelism (DOP) feedback** | July 2025 | [DOP Feedback](/sql/relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback?view=azuresqldb-current&preserve-view=true) is now generally available for Azure SQL Database. For more information, see [Smarter Parallelism: Degree of parallelism feedback in SQL Server 2025](https://techcommunity.microsoft.com/blog/sqlserver/smarter-parallelism-degree-of-parallelism-feedback-in-sql-server-2025/4431318). |
6969
| **Audit re-architecture** | July 2025 | Increased availability and reliability of server audits through a re-architecture of auditing in Azure SQL Database that is closely aligned with SQL Server and Azure SQL Managed Instance. For more information, see [Auditing](auditing-overview.md#enhancements-to-performance-availability-and-reliability-in-server-auditing-for-azure-sql-database-july-2025-ga).|
7070
| **Hyperscale increased log generation rate** | May 2025 | The transaction log generation rate in Azure SQL Database Hyperscale single databases has been increased from 100 MiB/s to 150 MiB/s for premium-series and premium-series memory optimized hardware. For more information, read [Blog: Enhancements to Azure SQL Database Hyperscale](https://aka.ms/HSenhancements).|
@@ -102,6 +102,8 @@ Learn about significant changes to the Azure SQL Database documentation. For pre
102102

103103
| Changes | Details |
104104
| --- | --- |
105+
| **UNISTR** | Azure SQL Database now supports the `UNISTR`. This syntax is now generally available. For more information, see [UNISTR (Transact-SQL)](/sql/t-sql/functions/unistr-transact-sql). |
106+
| **\| \| and \| \| = string concatenation support** | Azure SQL Database now supports \| \| and \| \| = compound assignment T-SQL syntax. This syntax is now generally available. For more information, see [&#124;&#124; (String concatenation)](/sql/t-sql/language-elements/string-concatenation-pipes-transact-sql) and [&#124;&#124;= (Compound assignment)](/sql/t-sql/language-elements/compound-assignment-pipes-transact-sql). |
105107
| **Degrees of Parallelism (DOP) feedback** | [DOP Feedback](/sql/relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback?view=azuresqldb-current&preserve-view=true) is now generally available for Azure SQL Database. For more information, see [Smarter Parallelism: Degree of parallelism feedback in SQL Server 2025](https://techcommunity.microsoft.com/blog/sqlserver/smarter-parallelism-degree-of-parallelism-feedback-in-sql-server-2025/4431318). |
106108
| **Convert to Hyperscale with geo-replicas (preview)** |The ability to [convert a geo-replicated database non-Hyperscale database to Hyperscale](convert-to-hyperscale.md) using T-SQL, REST API, PowerShell, or Azure CLI is currently a preview feature. For more information, see [Blog: Hyperscale conversion support for geo-replicas](https://aka.ms/hs-conversion-geodr-preview). |
107109
| **Audit re-architecture GA** | Enhancements to performance, availability, and reliability in server auditing for Azure SQL Database. For more information, see [Auditing](auditing-overview.md#enhancements-to-performance-availability-and-reliability-in-server-auditing-for-azure-sql-database-july-2025-ga). |

0 commit comments

Comments
 (0)