Skip to content

Commit 1ad109c

Browse files
authored
Merge pull request #33913 from MicrosoftDocs/main
4/23/2025 PM Publish
2 parents cbc04f0 + 647411e commit 1ad109c

File tree

2 files changed

+7
-3
lines changed

2 files changed

+7
-3
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article discusses the Transact-SQL (T-SQL) differences between
44
author: danimir
55
ms.author: danil
66
ms.reviewer: mathoma, bonova, danil, randolphwest
7-
ms.date: 02/17/2025
7+
ms.date: 04/23/2025
88
ms.service: azure-sql-managed-instance
99
ms.subservice: service-overview
1010
ms.topic: reference
@@ -423,7 +423,7 @@ For more information about configuring transactional replication, see the follow
423423
Resource governor is supported. However, there are several behavior differences:
424424

425425
- To modify resource governor configuration in SQL Managed Instance, you must be in the context of the `master` database on the primary replica.
426-
- 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`.
426+
- 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`.
427427
- 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).
428428
- The maximum number of resource pools you can create is 40.
429429

docs/sql-server/azure-arc/release-notes.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Latest release notes for SQL Server enabled by Azure Arc
44
author: anosov1960
55
ms.author: sashan
66
ms.reviewer: mikeray, randolphwest
7-
ms.date: 03/12/2025
7+
ms.date: 04/14/2025
88
ms.topic: conceptual
99
ms.custom:
1010
- ignite-2023
@@ -23,6 +23,10 @@ This article lists:
2323

2424
Extension versions are cumulative. Higher extension versions include all of the updates from previous versions. A release might include internal features. If the version release notes don't describe features, then the updates were internal.
2525

26+
## April 14, 2025
27+
28+
**Extension version**: `1.1.3021.274`
29+
2630
## March 11, 2025
2731

2832
**Extension version**: `1.1.2986.256`

0 commit comments

Comments
 (0)