Merge branch 'MicrosoftDocs:main' into patch-13

Author: MikeRayMSFT

.github/workflows/allow-signoff-for-files.yml

@@ -30,7 +30,6 @@ jobs:
                     "docs/database-engine/availability-groups/windows/contained-availability-groups-overview.md",
                     "docs/t-sql/statements/create-availability-group-transact-sql.md",
                     "docs/database-engine/configure-windows/server-configuration-options-sql-server.md",
-                    "docs/toc.yml",
                     "docs/database-engine/availability-groups/windows/availability-group-lease-healthcheck-timeout.md",
                     "docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md"
                 ]'

azure-sql/database/authentication-azure-ad-only-authentication-create-server.md

@@ -44,7 +44,7 @@ The following section provides you with examples and scripts on how to create a
 In our examples, we're enabling Microsoft Entra-only authentication during server or managed instance creation, with a system assigned server admin and password. This will prevent server admin access when Microsoft Entra-only authentication is enabled, and only allows the Microsoft Entra admin to access the resource. It's optional to add parameters to the APIs to include your own server admin and password during server creation. However, the password can't be reset until you disable Microsoft Entra-only authentication. An example of how to use these optional parameters to specify the server admin login name is presented in the [PowerShell](?tabs=azure-powershell#azure-sql-database) tab on this page.
 
 > [!NOTE]
-> To change the existing properties after server or managed instance creation, other existing APIs should be used. For more information, see [Managing Microsoft Entra-only authentication using APIs](authentication-azure-ad-only-authentication.md#managing-azure-ad-only-authentication-using-apis) and [Configure and manage Microsoft Entra authentication with Azure SQL](authentication-aad-configure.md).
+> To change the [Microsoft Entra-only authentication](authentication-azure-ad-only-authentication.md) property after server or managed instance creation, other existing APIs should be used. For more information, see [Managing Microsoft Entra-only authentication using APIs](authentication-azure-ad-only-authentication.md#managing-azure-ad-only-authentication-using-apis).
 > 
 > If Microsoft Entra-only authentication is set to false, which it is by default, a server admin and password will need to be included in all APIs during server or managed instance creation.
 

azure-sql/database/automatic-tuning-email-notifications-configure.md

@@ -4,7 +4,7 @@ description: Learn how to configure and manage Hyperscale named replica so that
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: atsingh, dinethi, rsetlem
-ms.date: 02/26/2024
+ms.date: 04/24/2025
 ms.service: azure-sql-database
 ms.subservice: scale-out
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
@@ -226,6 +226,19 @@ DELETE https://management.azure.com/subscriptions/00000000-1111-2222-3333-444444
 > [!IMPORTANT]  
 > Named replicas will be automatically removed when the primary replica from which they have been created is deleted.
 
+## Optimizing named replica configuration
+
+It is recommended to configure the named replica with the same compute size (vCores) as the primary replica. If the primary replica experiences a heavy write workload, a named replica with a lower compute size might not be able to keep up, causing replication lag. To maintain the recoverability SLAs, primary's transaction log rate can be temporarily reduced to allow its secondaries to catch up.
+
+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.
+- 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).
+
+For more information, see to the [Azure SQL Database Hyperscale Performance Diagnostics](hyperscale-performance-diagnostics.md#reduced-log-rate-waits).
+
+
 ## Related content
 
 - [Hyperscale secondary replicas](service-tier-hyperscale-replicas.md)

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

@@ -49,7 +49,7 @@ In order to use the **Windows** authentication metadata mode, the user environme
 
 The **Windows** authentication metadata mode helps modernize authentication for application, and unblocks migration challenges to SQL Managed Instance. Here are some common scenarios where the **Windows** authentication metadata mode can be used to address customer challenges:
 
-- The complexities of setting up [Windows Authentication for Azure SQL Managed Instance using Microsoft Entra ID and Kerberos](winauth-azuread-setup.md).
+- The overhead of migrating Windows logins to Microsoft Entra ID for [Windows authentication with Azure SQL Managed Instance using Microsoft Entra ID and Kerberos](winauth-azuread-setup.md).
 - Read-only replica failovers in [Managed Instance link](managed-instance-link-feature-overview.md).
 - Synchronization of [Microsoft Entra authentication for SQL Server](/sql/relational-databases/security/authentication-access/azure-ad-authentication-sql-server-overview).
 

azure-sql/managed-instance/native-windows-principals.md

@@ -192,7 +192,7 @@ Using the same time zone across a primary and secondary instance in a failover g
 | India Standard Time | (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi |
 | Sri Lanka Standard Time | (UTC+05:30) Sri Jayawardenepura |
 | Nepal Standard Time | (UTC+05:45) Kathmandu |
-| Central Asia Standard Time | (UTC+06:00) Nur-Sultan |
+| Central Asia Standard Time | (UTC+06:00) Astana |
 | Bangladesh Standard Time | (UTC+06:00) Dhaka |
 | Omsk Standard Time | (UTC+06:00) Omsk |
 | Myanmar Standard Time | (UTC+06:30) Yangon (Rangoon) |

azure-sql/managed-instance/timezones-overview.md

@@ -4,7 +4,7 @@ description: This article discusses the Transact-SQL (T-SQL) differences between
 author: danimir
 ms.author: danil
 ms.reviewer: mathoma, bonova, danil, randolphwest
-ms.date: 02/17/2025
+ms.date: 04/23/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: reference
@@ -423,7 +423,7 @@ For more information about configuring transactional replication, see the follow
 Resource governor is supported. However, there are several behavior differences:
 
 - To modify resource governor configuration in SQL Managed Instance, you must be in the context of the `master` database on the primary replica.
-- Resource governor configuration changes made on the primary replica propagate to all secondary replicas. However, changes to the currently effective configuration on a secondary replica might not be immediate. To make the changes effective on a secondary replica, [connect](../database/read-scale-out.md#connect-to-a-read-only-replica) to the replica and execute `ALTER RESOURCE GOVERNOR RECONFIGURE`.
+- Resource governor configuration changes made on the primary replica propagate to all secondary replicas. However, changes to the currently effective configuration on a secondary replica might not be immediate. To make the changes effective on a secondary replica, [connect](../database/read-scale-out.md#connect-to-a-read-only-replica) to the `master` database on a secondary replica and execute `ALTER RESOURCE GOVERNOR RECONFIGURE`.
 - In SQL Server, if the `REQUEST_MAX_CPU_TIME_SEC` setting is configured for a workload group and a batch request exceeds the configured CPU time, the `cpu_threshold_exceeded` event fires but the request is not terminated unless a trace flag is enabled. In SQL Managed Instance, the same event fires and the request is always terminated. For more information, see [REQUEST_MAX_CPU_TIME_SEC](/sql/t-sql/statements/create-workload-group-transact-sql#request_max_cpu_time_sec--value).
 - The maximum number of resource pools you can create is 40.
 

azure-sql/managed-instance/transact-sql-tsql-differences-sql-server.md

@@ -38,7 +38,7 @@ Before you complete the instructions in this article, you should already have:
 
 ## Add Azure shared disk
 
-[Deploy a managed with the shared disk feature enabled](/azure/virtual-machines/disks-shared-enable#deploy-shared-disks). Set `maxShares` to **align with the number of cluster nodes** to make the disk shareable across all FCI nodes.
+[Deploy a managed disk with the shared disk feature enabled](/azure/virtual-machines/disks-shared-enable#deploy-shared-disks). Set `maxShares` to **align with the number of cluster nodes** to make the disk shareable across all FCI nodes.
 Premium SSD, Premium SSDv2 and Ultra Disk are supported disk types to use with a SQL Server failover cluster instance. 
 
 Use zone-redundant storage (ZRS) whenever possible. 

azure-sql/virtual-machines/windows/failover-cluster-instance-azure-shared-disks-manually-configure.md

@@ -31,10 +31,7 @@ To create the tables necessary for the code samples to run correctly, you must r
 USE AdventureWorks2022;
 GO
 
-IF EXISTS (SELECT * FROM dbo.sysobjects   
- WHERE id = object_id(N'[dbo].[BulkCopyDemoMatchingColumns]')  
- AND OBJECTPROPERTY(id, N'IsUserTable') = 1)  
-    DROP TABLE [dbo].[BulkCopyDemoMatchingColumns]  
+DROP TABLE IF EXISTS [dbo].[BulkCopyDemoMatchingColumns]  
 
 CREATE TABLE [dbo].[BulkCopyDemoMatchingColumns]([ProductID] [int] IDENTITY(1,1) NOT NULL,  
     [Name] [nvarchar](50) NOT NULL,  
@@ -44,10 +41,7 @@ CREATE TABLE [dbo].[BulkCopyDemoMatchingColumns]([ProductID] [int] IDENTITY(1,1)
     [ProductID] ASC  
 ) ON [PRIMARY]) ON [PRIMARY]  
 
-IF EXISTS (SELECT * FROM dbo.sysobjects   
- WHERE id = object_id(N'[dbo].[BulkCopyDemoDifferentColumns]')  
- AND OBJECTPROPERTY(id, N'IsUserTable') = 1)  
-    DROP TABLE [dbo].[BulkCopyDemoDifferentColumns]  
+DROP TABLE IF EXISTS [dbo].[BulkCopyDemoDifferentColumns]  
 
 CREATE TABLE [dbo].[BulkCopyDemoDifferentColumns]([ProdID] [int] IDENTITY(1,1) NOT NULL,  
     [ProdNum] [nvarchar](25) NOT NULL,  
@@ -57,10 +51,7 @@ CREATE TABLE [dbo].[BulkCopyDemoDifferentColumns]([ProdID] [int] IDENTITY(1,1) N
     [ProdID] ASC  
 ) ON [PRIMARY]) ON [PRIMARY]  
 
-IF EXISTS (SELECT * FROM dbo.sysobjects   
- WHERE id = object_id(N'[dbo].[BulkCopyDemoOrderHeader]')  
- AND OBJECTPROPERTY(id, N'IsUserTable') = 1)  
-    DROP TABLE [dbo].[BulkCopyDemoOrderHeader]  
+DROP TABLE IF EXISTS [dbo].[BulkCopyDemoOrderHeader]  
 
 CREATE TABLE [dbo].[BulkCopyDemoOrderHeader]([SalesOrderID] [int] IDENTITY(1,1) NOT NULL,  
     [OrderDate] [datetime] NOT NULL,  
@@ -70,10 +61,7 @@ CREATE TABLE [dbo].[BulkCopyDemoOrderHeader]([SalesOrderID] [int] IDENTITY(1,1)
     [SalesOrderID] ASC  
 ) ON [PRIMARY]) ON [PRIMARY]  
 
-IF EXISTS (SELECT * FROM dbo.sysobjects   
- WHERE id = object_id(N'[dbo].[BulkCopyDemoOrderDetail]')  
- AND OBJECTPROPERTY(id, N'IsUserTable') = 1)  
-    DROP TABLE [dbo].[BulkCopyDemoOrderDetail]  
+DROP TABLE IF EXISTS [dbo].[BulkCopyDemoOrderDetail]  
 
 CREATE TABLE [dbo].[BulkCopyDemoOrderDetail]([SalesOrderID] [int] NOT NULL,  
     [SalesOrderDetailID] [int] NOT NULL,