20250819 database replicas

Author: WilliamDAssafMSFT

.openpublishing.redirection.json

@@ -67588,6 +67588,11 @@
       "source_path": "docs/relational-databases/sql-server-configuration-manager.md",
       "redirect_url": "/sql/tools/configuration-manager/sql-server-configuration-manager",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/relational-databases/system-dynamic-management-views/sys-dm-hs-database-log-rate.md",
+      "redirect_url": "/sql/relational-databases/system-functions/sys-dm-hs-database-log-rate",
+      "redirect_document_id": false
     }
   ]
 }

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: 07/28/2025
+ms.date: 08/11/2025
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: whats-new
@@ -63,6 +63,7 @@ The following table lists features of Azure SQL Database that have been made gen
 
 | Feature | GA Month | Details |
 | --- | --- | --- |
+| **sys.dm_hs_database_replicas** | August 2025 | You can query the details of Azure SQL Database Hyperscale replicas with the new dynamic management view (DMV) [sys.dm_hs_database_replicas](/sql/relational-databases/system-functions/sys-dm-hs-database-replicas).|
 | **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).|
 | **\|\| (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.|
 | **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). |
@@ -86,18 +87,17 @@ The following table lists features of Azure SQL Database that have been made gen
 | **Maintenance window support for named replicas** |August 2024|[Maintenance window](maintenance-window.md) support for named replicas is now generally available. For more information, see [General Availability: Maintenance window support for Azure SQL Database Hyperscale named replica](https://aka.ms/MWsupportforNR).|
 | **Maintenance window support for Hyperscale** | August 2024| [Maintenance window](maintenance-window.md) support for Hyperscale databases is now generally available. |
 | **Automatic backups on secondary replicas** | August 2024 | Mitigate the performance impact on your workload by taking [automated backups from the non-readable secondary replica](automated-backups-overview.md#automatic-backups-on-secondary-replicas) in the Business Critical service tier. |
-| **Database compatibility level 160 is now default** | June 2024 | [Database compatibility level 160](/sql/t-sql/statements/alter-database-transact-sql-compatibility-level?view=azuresqldb-current&preserve-view=true) is now the default for new databases created in Azure SQL Database. For more information on this announcement, see [General availability: Database compatibility level 160 in Azure SQL Database](https://techcommunity.microsoft.com/t5/azure-sql-blog/general-availability-database-compatibility-level-160-in-azure/ba-p/4172039). |
-| **Hyperscale named replica zone redundant support** | June 2024 | [Zone redundancy support for Hyperscale named replicas](https://techcommunity.microsoft.com/blog/azuresqlblog/general-availability-maintenance-window-support-for-azure-sql-database-hyperscal/4207651) is now generally available. For more information, see [Hyperscale secondary replicas](service-tier-hyperscale-replicas.md). |
-| **License-free standby replica** | May 2024 | Save on licensing costs by configuring your [secondary database replica for disaster recovery standby](standby-replica-how-to-configure.md). |
-| **Elastic jobs** | April 2024 | [Elastic jobs, now generally available](https://techcommunity.microsoft.com/t5/azure-sql-blog/general-availability-elastic-jobs-in-azure-sql-database/ba-p/4087140), are the SQL Server Agent replacement for Azure SQL Database. [Elastic jobs](elastic-jobs-overview.md) now support Microsoft Entra ID authentication, private endpoints, management via REST APIs, Azure Alerts, and more new features since preview began. |
-| **Maintenance window advance notifications** | March 2024 | [Advance notifications](advance-notifications.md) are now generally available for databases configured to use a nondefault [maintenance window](maintenance-window.md). |
-| **Azure SQL triggers for Azure Functions** | March 2024 | Azure Functions supports [function triggers for Azure SQL Database](/azure/azure-functions/functions-bindings-azure-sql-trigger). |
-| **Serverless Hyperscale** | February 2024 | Automatically scale your Hyperscale databases up and down based on usage when using the [serverless compute tier](serverless-tier-overview.md). |
 
 ## Documentation changes
 
 Learn about significant changes to the Azure SQL Database documentation. For previous years, see the [What's new archive](doc-changes-updates-release-notes-whats-new-archive.md).
 
+### August 2025
+
+| Changes | Details |
+| --- | --- |
+| **sys.dm_hs_database_replicas** | You can query the details of Azure SQL Database Hyperscale replicas with the new dynamic management view (DMV) [sys.dm_hs_database_replicas](/sql/relational-databases/system-functions/sys-dm-hs-database-replicas).|
+
 ### July 2025
 
 | Changes | Details |

azure-sql/database/hyperscale-named-replica-configure.md

@@ -235,7 +235,7 @@ It is recommended to configure the named replica with the same compute size (vCo
 
 If you choose to create the named replica with a different compute size (vCores) than the primary, monitor the log IO rate on the primary over time. This helps estimate the minimal compute size required for the named replica to sustain the replication load. For more information, consider the following objects:
 
-- The [sys.dm_hs_database_log_rate()](/sql/relational-databases/system-dynamic-management-views/sys-dm-hs-database-log-rate) dynamic management function (DMF) provides additional details to help understand log rate reduction, if any. It can indicate which specific secondary replica is behind in applying log records and the total size of the unapplied transaction log.
+- The [sys.dm_hs_database_log_rate()](/sql/relational-databases/system-functions/sys-dm-hs-database-log-rate) dynamic management function (DMF) provides additional details to help understand log rate reduction, if any. It can indicate which specific secondary replica is behind in applying log records and the total size of the unapplied transaction log.
 - To retrieve historical log IO data, use [sys.resource_stats](/sql/relational-databases/system-catalog-views/sys-resource-stats-azure-sql-database) view.
 - For recent log IO data with higher granularity that better reflects short-term spikes, use [sys.dm_db_resource_stats](/sql/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database).
 

azure-sql/database/hyperscale-performance-diagnostics.md

@@ -38,7 +38,7 @@ The following wait types appear in [sys.dm_os_wait_stats](/sql/relational-databa
 | `RBIO_RG_STORAGE_CHECKPOINT` | Delayed log consumption on by a page server due to slow database checkpoint |
 | `RBIO_RG_MIGRATION_TARGET` | Delayed log consumption by the non-Hyperscale database during reverse migration |
 
-The [sys.dm_hs_database_log_rate()](/sql/relational-databases/system-dynamic-management-views/sys-dm-hs-database-log-rate) dynamic management function (DMF) provides additional details to help you understand log rate reduction, if any. For example, it can tell you which specific secondary replica is behind applying log records, and what is the total size of the not yet applied transaction log.
+The [sys.dm_hs_database_log_rate()](/sql/relational-databases/system-functions/sys-dm-hs-database-log-rate) dynamic management function (DMF) provides additional details to help you understand log rate reduction, if any. For example, it can tell you which specific secondary replica is behind applying log records, and what is the total size of the not yet applied transaction log.
 
 ## Page server reads
 

azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml

@@ -11,7 +11,7 @@ metadata:
   author: WilliamDAssafMSFT
   ms.author: wiassaf
   ms.reviewer: dfurman, mathoma, dinethi, blakhani, adbadram
-  ms.date: 06/30/2025
+  ms.date: 08/11/2025
 title: Azure SQL Database Hyperscale FAQ
 summary: |
   [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -549,10 +549,18 @@ sections:
           Yes. The [Column Master Key](/sql/t-sql/statements/create-column-master-key-transact-sql?view=azuresqldb-current&preserve-view=true) is stored in the user database and can be validated by executing the query `SELECT * FROM sys.column_master_keys`. Named replicas and high availability secondary replicas read data from the same page servers/storage layer as the primary Hyperscale database. Both types of replicas are synchronized with the primary Hyperscale database via the log service. A key change is considered a transaction and is automatically replicated to all secondary replicas.
 
       - question: |
-          Can I determine the name of a named replica associated with a value in the replica_id column in sys.dm_database_replica_states?
+          How do I query information about Hyperscale database secondary replicas?
 
         answer: |
-          Not when you query `sys.dm_database_replica_states` on the primary replica. However, you can connect to a named replica to determine its replica ID and other details using the following sample query:
+
+          You can connect to the primary replica and determine its replica ID and the details of other secondary replicas using the `sys.dm_hs_database_replicas` DMF. For more information, see [sys.dm_hs_database_replicas](/sql/relational-databases/system-functions/sys-dm-hs-database-replicas). The following example returns a row for each replica of a Hyperscale database named `Contosodb`. 
+
+          ```sql
+          SELECT replica_role_desc, replica_server_name, replica_id
+          FROM sys.dm_hs_database_replicas(DB_ID(N'Contosodb'));
+          ```
+
+          You can also connect to a secondary replica to determine its replica ID and other details. The following sample query of [sys.dm_database_replica_states](/sql/relational-databases/system-dynamic-management-views/sys-dm-database-replica-states-azure-sql-database) shows the details for the current replica context:
 
           ```sql
             SELECT replica_id,

azure-sql/database/service-tier-hyperscale-replicas.md

@@ -4,7 +4,7 @@ description: This article describes the different types of secondary replicas av
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: atsingh, arvindsh
-ms.date: 11/04/2024
+ms.date: 08/11/2025
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: overview
@@ -41,6 +41,15 @@ HA replicas use the same server and database name as the primary replica. Their
 
 There can be zero to four HA replicas. You can specify the number replicas during the creation of a new database, or update the number of replicas for an existing database. You can use the common management endpoints and tools (for example: Azure PowerShell, Azure CLI, Azure portal, REST API) to specify the number of HA replicas. Creating or removing HA replicas doesn't affect active connections on the primary replica.
 
+### Identify replicas
+
+You can identify all the Azure SQL Database Hyperscale replicas and their roles when connected to a primary replica with the [sys.dm_hs_database_replicas (Transact-SQL)](/sql/relational-databases/system-functions/sys-dm-hs-database-replicas) dynamic management view (DMV). For example:
+
+```sql
+SELECT replica_role_desc, replica_server_name, replica_id
+FROM sys.dm_hs_database_replicas(DB_ID(N'Contosodb'));
+```
+
 ### Connect to an HA replica
 
 In Hyperscale databases, the `ApplicationIntent` argument in the connection string used by the client dictates whether the connection is routed to the read-write primary replica or to a read-only HA replica. If `ApplicationIntent` is set to `ReadOnly` and the database doesn't have a secondary replica, connection is routed to the primary replica and defaults to the `ReadWrite` behavior.

…ent-views/sys-dm-hs-database-log-rate.md …functions/sys-dm-hs-database-log-rate.mddocs/relational-databases/system-dynamic-management-views/sys-dm-hs-database-log-rate.md renamed to docs/relational-databases/system-functions/sys-dm-hs-database-log-rate.md docs/relational-databases/system-dynamic-management-views/sys-dm-hs-database-log-rate.md renamed to docs/relational-databases/system-functions/sys-dm-hs-database-log-rate.md

@@ -1,10 +1,10 @@
 ---
 title: "sys.dm_hs_database_log_rate (Transact-SQL)"
-description: sys.dm_hs_database_log_rate (Transact-SQL)
+description: The sys.dm_hs_database_log_rate dynamic management function returns information about log generation rate in Azure SQL Database Hyperscale.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: dfurman, atsingh
-ms.date: 12/18/2024
+ms.date: 08/11/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -15,6 +15,8 @@ f1_keywords:
   - "dm_hs_database_log_rate_TSQL"
 helpviewer_keywords:
   - "sys.dm_hs_database_log_rate catalog view"
+  - "sys.dm_hs_database_log_rate function"
+  - "sys.dm_hs_database_log_rate DMF"
 dev_langs:
   - "TSQL"
 monikerRange: "=azuresqldb-current"
@@ -23,17 +25,16 @@ monikerRange: "=azuresqldb-current"
 
 [!INCLUDE [Azure SQL Database](../../includes/applies-to-version/asdb.md)]
 
-Each resultset row returns a component that controls (reduces) log generation rate in a Hyperscale database. There are multiple [components in Hyperscale tier architecture](/azure/azure-sql/database/hyperscale-architecture) that could contribute to the reducing log generation rate.
+The `sys.dm_hs_database_log_rate` dynamic management function (DMF) returns information about log generation rate in Azure SQL Database Hyperscale.
+
+Each row in the result set represents a component that controls (reduces) log generation rate in a Hyperscale database. There are multiple [components in Hyperscale tier architecture](/azure/azure-sql/database/hyperscale-architecture) that could reduce log generation rate to keep database performance stable and balanced.
 
 Certain types of components, such as secondary compute replicas or page servers, can temporarily reduce log generation rate on the primary compute replica to ensure the overall database health and stability.
 
 If log generation rate is not reduced by any component, a row is returned for the primary compute replica component, showing the maximum allowed log generation rate for the database.
 
 This dynamic management function returns rows only when the session is connected to the primary replica.
 
-> [!NOTE]
-> The `sys.dm_hs_database_log_rate` dynamic management function currently applies to Azure SQL Database Hyperscale tier only.
-
 ## Syntax
 
 ```syntaxsql
@@ -48,9 +49,9 @@ sys.dm_hs_database_log_rate (
 
 *database_id* is an **integer** representing the database ID, with no default value. Valid inputs are either a database ID or `NULL`.
 
-Specified `database_id`: Returns a row for that specific database.
+When a `database_id` is provided, `sys.dm_hs_database_log_rate` returns a row for that specific database.
 
-`NULL`: For a single database, returns a row for the current database. For a database in an elastic pool, returns rows for all databases in the pool where the caller has sufficient [permissions](#permissions).
+When not provided or when `NULL` is provided, for a single database, returns a row for the current database. For a database in an elastic pool, returns rows for all databases in the pool where the caller has sufficient [permissions](#permissions).
 
 The built-in function [DB_ID](../../t-sql/functions/db-id-transact-sql.md) can be specified.
 
@@ -72,6 +73,8 @@ The built-in function [DB_ID](../../t-sql/functions/db-id-transact-sql.md) can
 
 ## Remarks
 
+The `sys.dm_hs_database_log_rate` dynamic management function applies to Azure SQL Database Hyperscale tier only.
+
 In the Hyperscale service tier of Azure SQL Database, the log service ensures that the distributed components don't get far behind in applying transaction log. This is required to maintain the overall system health and stability. When components are behind and their catch-up rate is less than current log generation rate, the log service reduces the log generation rate on the primary. The `sys.dm_hs_database_log_rate()` DMF can be used to understand which component is causing the reduction in log rate and to what extent, and for how long the reduction of log rate might last.
 
 For more context about log rate reduction, see [Performance diagnostics in Hyperscale](/azure/azure-sql/database/hyperscale-performance-diagnostics?view=azuresql-db&preserve-view=true).
@@ -102,7 +105,8 @@ FROM sys.dm_hs_database_log_rate(NULL);
 
 ## Related content
 
-- [sys.dm_database_replica_states (Azure SQL Database)](sys-dm-database-replica-states-azure-sql-database.md?view=azuresqldb-current&preserve-view=true)
+- [sys.dm_database_replica_states (Azure SQL Database) (Transact-SQL)](../system-dynamic-management-views/sys-dm-database-replica-states-azure-sql-database.md?view=azuresqldb-current&preserve-view=true)
+- [sys.dm_hs_database_replicas (Transact-SQL)](sys-dm-hs-database-replicas.md?view=azuresqldb-current&preserve-view=true)
 - [sys.dm_exec_requests (Transact-SQL)](../system-dynamic-management-views/sys-dm-exec-requests-transact-sql.md?view=azuresqldb-current&preserve-view=true)
 - [sys.dm_os_wait_stats (Transact-SQL)](../system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md?view=azuresqldb-current&preserve-view=true)
 - [DATABASEPROPERTYEX (Transact-SQL)](../../t-sql/functions/databasepropertyex-transact-sql.md?view=azuresqldb-current&preserve-view=true)