Merge pull request #37056 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-13 22:30 UTC

Author: learn-build-service-prod[bot]

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

@@ -5,7 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma, randolphwest
-ms.date: 03/24/2026
+ms.date: 04/13/2026
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: whats-new
@@ -57,10 +57,12 @@ The following table lists the features of Azure SQL Database that are currently
 | **Multiple secondaries for failover groups** | You can [configure multiple secondary servers for failover groups](failover-group-sql-db.md#multiple-secondaries) in Azure SQL Database. |
 | **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. |
 | **New Query editor experience in the Azure portal** | As of March 2026, there's a new [query editor in the Azure portal](query-editor.md) that allows you to run queries against your Azure SQL Database directly from a web browser. |
+| **Query Store for readable secondary replicas** | [Query Store for readable secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas) enables Query Store insights for workloads that run on secondary replicas. When enabled, secondary replicas stream query execution information (such as runtime and wait statistics) to the primary replica, where the data is persisted in Query Store and made visible across all replicas. |
 | **Restart database in the Azure portal** | You can [restart your SQL database or elastic pool](restart-database.md) from the Azure portal. |
 | **Soft delete retention for logical server** | You can [configure a soft delete retention period](deleted-logical-server-restore.md) for a logical server and restore a deleted server within the retention period.|
 | **Vector indexing and VECTOR_SEARCH enhancements** | DiskANN vector indexes are now in preview with full DML support, iterative filtering, the new `SELECT TOP (N) WITH APPROXIMATE` syntax, and the `FORCE_ANN_ONLY` table hint. Earlier vector index versions and the `TOP_N` parameter are deprecated. For more information, see [CREATE VECTOR INDEX](/sql/t-sql/statements/create-vector-index-transact-sql?view=azuresqldb-current&preserve-view=true) and [VECTOR_SEARCH](/sql/t-sql/functions/vector-search-transact-sql?view=azuresqldb-current&preserve-view=true). |
 
+
 ## General availability (GA)
 
 The following table lists features of Azure SQL Database that have been made generally available (GA) within the last 12 months:

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

@@ -5,7 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: wiassaf, randolphwest
-ms.date: 03/27/2026
+ms.date: 04/13/2026
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: whats-new
@@ -43,7 +43,7 @@ The following table lists the features of Azure SQL Managed Instance that are cu
 |[SDK-style SQL project](/sql/tools/sql-database-projects/sql-database-projects) | Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Visual Studio Code. SDK-style SQL projects are especially advantageous for applications shipped through pipelines or built in cross-platform environments.|
 |[Service Broker](/sql/database-engine/configure-windows/sql-server-service-broker) | Support for cross-instance message exchange using Service Broker between instances of Azure SQL Managed Instance, and between SQL Server and Azure SQL Managed Instance. |
 |[Vector data type and functions](/sql/t-sql/data-types/vector-data-type?view=azuresqlmi-current&preserve-view=true) | Working with vector data is now easier in Azure SQL Managed Instance with the introduction of a new [vector data type](/sql/t-sql/data-types/vector-data-type?view=azuresqlmi-current&preserve-view=true) and [vector functions](/sql/t-sql/functions/vector-functions-transact-sql?view=azuresqlmi-current&preserve-view=true). For more information, see [Intelligent applications with Azure SQL Managed Instance](ai-artificial-intelligence-intelligent-applications.md#vectors). |
-
+| [Query Store for readable secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas) | Query Store for readable secondary replicas enables Query Store insights for workloads that run on secondary replicas. When enabled, secondary replicas stream query execution information (such as runtime and wait statistics) to the primary replica, where the data is persisted in Query Store and made visible across all replicas. |
 
 ## General availability (GA)
 
@@ -88,6 +88,12 @@ Learn about significant changes to the Azure SQL Managed Instance documentation.
 |**Migrate multiple DBs through Azure Arc** | You can now migrate multiple databases simultaneously from a SQL Server instance enabled with Azure Arc to Azure SQL Managed Instance by using the Managed Instance link. For more information, see [Migrate SQL Server database to Azure SQL Managed Instance](/sql/sql-server/azure-arc/migration-sql-mi-prepare-link). |
 | **SQL Server 2025 update policy GA** | Align your SQL managed instance database format with the SQL Server 2025 Database Engine. This update policy is now generally available. For more information, review [SQL Server 2025 update policy](update-policy.md#sql-server-2025-update-policy). |
 
+### February 2026
+
+| Changes | Details |
+| --- | --- |
+| **Query Store for readable secondary replicas preview** | Query Store for readable secondary replicas enables Query Store insights for workloads that run on secondary replicas. When enabled, secondary replicas stream query execution information (such as runtime and wait statistics) to the primary replica, where the data is persisted in Query Store and made visible across all replicas. This feature is in preview for Azure SQL Managed Instance configured with the [Always-up-to-date update policy](update-policy.md#always-up-to-date-update-policy), and is enabled by default. For more information, see [Query Store for readable secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas). |
+
 ### December 2025
 
 | Changes | Details |

azure-sql/managed-instance/update-policy.md

@@ -75,7 +75,7 @@ The following table lists all the features that are only available to instances
 
 | Update policy | Features |
 |---------|---------|
-| *Always-up-to-date* update policy | - [Automatic index compaction](/sql/relational-databases/indexes/automatic-index-compaction) <br /> - All features available with the *SQL Server 2025* update policy are also available to instances with the *Always-up-to-date* update policy, other than the ability to restore databases to, or configure a link with bidirectional failover with, [!INCLUDE [sssql25-md](../../docs/includes/sssql25-md.md)]. |
+| *Always-up-to-date* update policy | - [Automatic index compaction](/sql/relational-databases/indexes/automatic-index-compaction)<br />- [Query Store for secondary replicas](/sql/relational-databases/performance/query-store-for-secondary-replicas)<br />- All features available with the *SQL Server 2025* update policy are also available to instances with the *Always-up-to-date* update policy, other than the ability to restore databases to, or configure a link with bidirectional failover with, [!INCLUDE [sssql25-md](../../docs/includes/sssql25-md.md)]. |
 | *SQL Server 2025* update policy | - [Azure SQL Managed Instance Mirroring in Fabric](/fabric/database/mirrored-database/azure-sql-managed-instance) <br /> - [Change event streaming (Preview)](/sql/relational-databases/track-changes/change-event-streaming/overview) <br /> - [DATEADD (Transact-SQL)](/sql/t-sql/functions/dateadd-transact-sql) <br /> - [Degree of parallelism (DOP) feedback](/sql/relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback?view=azuresqlmi-current&preserve-view=true) <br /> - [Fuzzy string matching](/sql/relational-databases/fuzzy-string-match/overview) <br /> - [Invoke an HTTPS REST endpoint SP](/sql/relational-databases/system-stored-procedures/sp-invoke-external-rest-endpoint-transact-sql) <br /> - [JSON data type](/sql/t-sql/data-types/json-data-type) <br /> - [JSON_ARRAYAGG](/sql/t-sql/functions/json-arrayagg-transact-sql) and [JSON_OBJECTAGG](/sql/t-sql/functions/json-objectagg-transact-sql) aggregate functions <br /> - [Link with bidirectional failover and disaster recovery with SQL Server 2025](managed-instance-link-disaster-recovery.md) <br /> - [Optimized locking](/sql/relational-databases/performance/optimized-locking?view=azuresqlmi-current&preserve-view=true) <br /> - [Regular expression functions](/sql/relational-databases/regular-expressions/overview) <br /> - [Restore database to SQL Server 2025](restore-database-to-sql-server.md) <br /> - [\|\| (String concatenation)](/sql/t-sql/language-elements/string-concatenation-pipes-transact-sql) <br /> - [\|\|= (Compound assignment)](/sql/t-sql/language-elements/compound-assignment-pipes-transact-sql) <br /> - [UNISTR (Transact-SQL)](/sql/t-sql/functions/unistr-transact-sql) <br /> - [Vector data type](/sql/t-sql/data-types/vector-data-type?view=azuresqlmi-current&preserve-view=true) <br /> - [Vector functions](/sql/t-sql/functions/vector-functions-transact-sql?view=azuresqlmi-current&preserve-view=true) |
 | *SQL Server 2022* update policy | - [Link with bidirectional failover and disaster recovery with SQL Server 2022](managed-instance-link-disaster-recovery.md) <br /> - [Restore database to SQL Server 2022](restore-database-to-sql-server.md)  |
 

docs/relational-databases/backup-restore/sql-server-backup-to-url.md

@@ -142,11 +142,13 @@ The following are security considerations and requirements when backing up to or
 
 ## Limitations of backup/restore to Azure Blob Storage
 
-- SQL Server limits the maximum backup size supported using a page blob to 1 TB. The maximum backup size supported using block blobs is limited to approximately 200 GB (50,000 blocks * 4 MB `MAXTRANSFERSIZE`). Block blobs support striping to support substantially larger backup sizes - the limit is a maximum of 64 URLs, which results in the following formula: `64 stripes * 50,000 blocks * 4MB maxtransfersize = 12.8 TB`.
+- SQL Server limits the maximum backup size supported using a page blob to 1 TB. The maximum backup size supported using block blobs is limited to approximately 195.3 GB (50,000 blocks * 4 MB `MAXTRANSFERSIZE`). Block blobs support striping to support substantially larger backup sizes - the limit is a maximum of 64 URLs, which results in the following formula: `64 stripes * 50,000 blocks * 4MB maxtransfersize = 12.8 TB`.
 
   > [!IMPORTANT]  
-  > Although the maximum backup size supported by a single block blob is 200 GB, it's possible for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to write in smaller block sizes, which can lead [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to reach the 50,000 block limit before the entire backup is transferred. Stripe backups (even if they're smaller than 200 GB) to avoid the block limit, especially when if you use differential or uncompressed backups.
+  > Although the maximum backup size supported by a single block blob is approximately 195.3 GB, it's possible for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to write in smaller block sizes, which can lead [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to reach the 50,000 block limit before the entire backup is transferred. Stripe backups (even if they're smaller than 200 GB) to avoid the block limit, especially when if you use differential or uncompressed backups.
 
+- Transaction log backups ignore the user-specified `MAXTRANSFERSIZE` when backing up to multiple backup files. Instead, 64KB is used if more than one file is specified, regardless of the `MAXTRANSFERSIZE` value in the backup command. Therefore, the maximum size of a transaction log backup to URL is approximately 195.3GB (50,000 blocks * 4 MB `MAXTRANSFERSIZE` * 1 file OR 50,000 blocks * 64 KB * 64 files). Compression can allow for a larger transaction log to be backed up, but compression ratios will vary.
+  
 - You can issue backup or restore statements by using Transact-SQL, SMO, PowerShell cmdlets, or the SQL Server Management Studio Backup or Restore wizard.
 
 - When backing up to an Azure Storage account, SQL Server only supports authentication with Shared Access Signature (SAS) tokens or storage account keys. All other authentication methods, including authentication with Microsoft Entra ID ([formerly Azure Active Directory](/entra/fundamentals/new-name)), aren't supported.

docs/relational-databases/performance/query-store-for-secondary-replicas.md

@@ -4,41 +4,45 @@ description: Query Store can be configured to monitor and tuning workloads on se
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: derekw, randolphwest, wiassaf
-ms.date: 01/27/2026
+ms.date: 04/14/2026
 ms.service: sql
 ms.subservice: performance
 ms.topic: concept-article
 ms.custom:
   - build-2025
 helpviewer_keywords:
   - "Query Store secondary replicas"
-monikerRange: ">=sql-server-ver16 || =azuresqldb-current"
+monikerRange: ">=sql-server-ver16 || =azuresqldb-current || =azuresqldb-mi-current"
 ---
-# Query Store for readable secondary replicas
+# Query Store for readable secondary replicas (preview)
 
 [!INCLUDE [sqlserver2022-asdb-asmi](../../includes/applies-to-version/sqlserver2022-asdb-asmi.md)]
 
 Query Store for readable secondary replicas enables Query Store insights for workloads that run on secondary replicas. When enabled, secondary replicas stream query execution information (such as runtime and wait statistics) to the primary replica, where the data is persisted in Query Store and made visible across all replicas.
 
+> [!NOTE]
+> Query store for readable secondary replicas is currently in preview in all SQL Database Engine platforms. 
+
 <a id="platform-support"></a>
 
 ## Availability
 
-Beginning with [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)], and in Azure SQL Database, Query Store for readable secondary replicas is enabled by default. 
+Query Store for readable secondary replicas is available starting in [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)], as well as Azure SQL Database and Azure SQL Managed Instance with the [Always-up-to-date update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy). For [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], Query Store for readable secondary replicas requires enabling trace flag 12606 to use the feature. For earlier versions of SQL Server and Azure SQL Managed Instance with other update policies, Query Store for readable secondary replicas isn't available.
 
 The following table summarizes the availability and the enabled state of Query store for readable secondaries.
 
 | Platform | Available | Enabled by default |
 | --- | --- | --- |
-| [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] | Yes | Yes (always enabled) |
+| [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] | Yes<sup>1</sup> | Yes (always enabled) |
 | [!INCLUDE [fabric-sqldb](../../includes/fabric-sqldb.md)] | Yes | Yes (always enabled) |
 | [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)]<sup>[AUTD](/azure/azure-sql/managed-instance/update-policy?view=azuresql-mi&preserve-view=true#always-up-to-date-update-policy)</sup> | Yes | Yes (always enabled) |
 | [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)]<sup>[2025](/azure/azure-sql/managed-instance/update-policy?view=azuresql-mi&preserve-view=true#sql-server-2025-update-policy)</sup> | No | No |
 | [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)]<sup>[2022](/azure/azure-sql/managed-instance/update-policy?view=azuresql-mi&preserve-view=true#sql-server-2022-update-policy)</sup> | No | No |
 | [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)] | Yes | No (can be enabled, per database) |
-| [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] | No\* | No |
+| [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] | No<sup>2</sup> | No |
 
-\* Query Store for readable secondaries remains in preview for [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], and is therefore **not** supported in production, and is disabled by default. To enable Query Store for readable secondaries in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] only, a trace flag 12606 is required to be enabled to the primary and all readable secondary replicas. Trace flag 12606 **is not** intended for production deployments that are based on [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)]. For more information, see [SQL Server 2022 release notes](../../sql-server/sql-server-2022-release-notes.md).
+<sup>1</sup> Query store for readable secondaries is not currently available in the Hyperscale service tier of Azure SQL Database.   
+<sup>2</sup> Query Store for readable secondaries remains in preview for [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], and is therefore **not** supported in production, and is disabled by default. To enable Query Store for readable secondaries in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] only, a trace flag 12606 is required to be enabled to the primary and all readable secondary replicas. Trace flag 12606 **is not** intended for production deployments that are based on [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)]. For more information, see [SQL Server 2022 release notes](../../sql-server/sql-server-2022-release-notes.md).
 
 ## Supported high availability scenarios