Skip to content

Commit 33003ec

Browse files
MikeRayMSFTMikeRayMSFT
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into 20221213-os-support-issue-8324
2 parents f1c1f74 + 39c0396 commit 33003ec

409 files changed

Lines changed: 1804 additions & 1432 deletions

File tree

Some content is hidden

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

‎azure-sql/database/auditing-overview.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ An auditing policy can be defined for a specific database or as a default [serve
8484

8585
## <a id="setup-auditing"></a>Set up auditing for your server
8686

87-
The default auditing policy includes all actions and the following set of action groups, which will audit all the queries and stored procedures executed against the database, as well as successful and failed logins:
87+
The default auditing policy includes the following set of action groups, which will audit all the queries and stored procedures executed against the database, as well as successful and failed logins:
8888

8989
- BATCH_COMPLETED_GROUP
9090
- SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP

‎azure-sql/database/authentication-azure-ad-logins-tutorial.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -148,13 +148,13 @@ In order to grant one of the special database roles to a user, the user must exi
148148
To add a user to a role, you can run the following query:
149149

150150
```sql
151-
ALTER ROLE [dbamanger] ADD MEMBER [AzureAD_object]
151+
ALTER ROLE [dbmanager] ADD MEMBER [AzureAD_object]
152152
```
153153

154154
To remove a user from a role, run the following query:
155155

156156
```sql
157-
ALTER ROLE [dbamanger] DROP MEMBER [AzureAD_object]
157+
ALTER ROLE [dbmanager] DROP MEMBER [AzureAD_object]
158158
```
159159

160160
`AzureAD_object` can be an Azure AD user, group, or service principal in Azure AD.
@@ -164,7 +164,7 @@ In our example, we created the user `bob@contoso.com`. Let's give the user the *
164164
1. Run the following query:
165165

166166
```sql
167-
ALTER ROLE [dbamanger] ADD MEMBER [bob@contoso.com]
167+
ALTER ROLE [dbmanager] ADD MEMBER [bob@contoso.com]
168168
ALTER ROLE [loginmanager] ADD MEMBER [bob@contoso.com]
169169
```
170170

‎azure-sql/database/recovery-using-backups.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ To restore a database by using the REST API:
180180
You can restore a deleted database to the deletion time, or an earlier point in time, on the same server by using the Azure portal, the Azure CLI, Azure PowerShell, and the Rest API.
181181

182182
> [!IMPORTANT]
183-
> If you delete a server, all its databases are also deleted and can't be recovered. You can't restore a deleted server.
183+
> If you delete a server, all its databases are also deleted and can't be recovered. You can't restore a deleted server. If LTR backups were taken, individual databases can be restored to a different server.
184184
185185
### [Azure portal](#tab/azure-portal)
186186

‎azure-sql/database/service-tiers-sql-database-vcore.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: The vCore purchasing model lets you independently scale compute and
44
author: WilliamDAssafMSFT
55
ms.author: wiassaf
66
ms.reviewer: sashan, moslake, mathoma
7-
ms.date: 11/28/2022
7+
ms.date: 12/13/2022
88
ms.service: sql-database
99
ms.subservice: performance
1010
ms.topic: conceptual
@@ -162,7 +162,7 @@ Standard-series (Gen5) hardware is available in all public regions worldwide.
162162
#### <a id="hyperscale-premium-series-availability"></a> Hyperscale premium-series
163163

164164
Hyperscale service tier (currently in preview) premium-series and premium-series memory optimized hardware is available in the following regions:
165-
Canada Central, East US, South Central US, UK South, West US 2.
165+
Australia East, Canada Central, East US, Japan East, North Europe, South Central US, UK South, West Europe, West US 1, West US 2.
166166

167167
#### Fsv2-series
168168

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,8 +144,8 @@ Learn about significant changes to the Azure SQL Managed Instance documentation.
144144

145145
| Changes | Details |
146146
| --- | --- |
147-
| **Windows Auth for Azure Active Directory principals** | Kerberos authentication for Azure Active Directory (Azure AD) enables Windows Authentication access to Azure SQL Managed Instance. This feature is now generally available (GA). To learn more, review [Windows Auth for Azure Active Directory principals](winauth-azuread-overview.md). |
148-
|**Query Store hints**| Use query hints to optimize your query execution via the OPTION clause. This feature is now generally available (GA). To learn more, review, [Query Store hints](/sql/relational-databases/performance/query-store-hints?view=azuresqldb-mi-current&preserve-view=true)|
147+
| **Windows Auth for Azure Active Directory principals GA** | Kerberos authentication for Azure Active Directory (Azure AD) enables Windows Authentication access to Azure SQL Managed Instance. This feature is now generally available (GA). To learn more, review [Windows Auth for Azure Active Directory principals](winauth-azuread-overview.md). |
148+
|**Query Store hints GA**| Use query hints to optimize your query execution via the OPTION clause. This feature is now generally available (GA). To learn more, review, [Query Store hints](/sql/relational-databases/performance/query-store-hints?view=azuresqldb-mi-current&preserve-view=true)|
149149

150150
### July 2022
151151

‎azure-sql/managed-instance/frequently-asked-questions-faq.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -390,7 +390,7 @@ sections:
390390
391391
### What is the recommended way to connect managed instances placed in different regions?
392392
393-
Global virtual network peering (VNet peering) is the recommended method to connect two managed instances in different regions. Express Route circuit peering is an alternative option. If neither option is possible in your environment, the only other connectivity method is a Site-to-Site VPN connection. Configure Site-to-Site VPN by using the [Azure portal](/azure/vpn-gateway/tutorial-site-to-site-portal), [PowerShell](/azure/vpn-gateway/vpn-gateway-create-site-to-site-rm-powershell), or the [Azure CLI](/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-cli)
393+
Both global virtual network peering (VNet peering) and [Azure virtual WAN](/azure/virtual-wan/virtual-wan-about) are recommended methods to connect two managed instances in different regions. Express Route circuit peering is an alternative option. If neither option is possible in your environment, the only other connectivity method is a Site-to-Site VPN connection. Configure Site-to-Site VPN by using the [Azure portal](/azure/vpn-gateway/tutorial-site-to-site-portal), [PowerShell](/azure/vpn-gateway/vpn-gateway-create-site-to-site-rm-powershell), or the [Azure CLI](/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-cli)
394394
395395
### Does SQL Managed Instance support Global VNet Peering?
396396

‎azure-sql/managed-instance/sql-managed-instance-paas-overview.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -172,9 +172,9 @@ SQL Managed Instance authentication refers to how users prove their identity whe
172172

173173
This authentication method uses identities managed by Azure Active Directory and is supported for managed and integrated domains. Use Active Directory authentication (integrated security) [whenever possible](/sql/relational-databases/security/choose-an-authentication-mode).
174174

175-
- **Windows Authentication for Azure AD Principals (Preview)**:
175+
- **Windows Authentication for Azure AD Principals**:
176176

177-
[Kerberos authentication for Azure AD Principals](../managed-instance/winauth-azuread-overview.md) (Preview) enables Windows Authentication for Azure SQL Managed Instance. Windows Authentication for managed instances empowers customers to move existing services to the cloud while maintaining a seamless user experience and provides the basis for infrastructure modernization.
177+
[Kerberos authentication for Azure AD Principals](../managed-instance/winauth-azuread-overview.md) enables Windows Authentication for Azure SQL Managed Instance. Windows Authentication for managed instances empowers customers to move existing services to the cloud while maintaining a seamless user experience and provides the basis for infrastructure modernization.
178178

179179
### Authorization
180180

‎azure-sql/virtual-machines/windows/availability-group-listener-powershell-configure.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,9 @@ If you are restricting access with an Azure Network Security Group, ensure that
5757

5858
[Azure load balancer](/azure/load-balancer/load-balancer-overview) is available in two SKUs: Basic & Standard. The standard load balancer is recommended. If the virtual machines are in an availability set, basic load balancer is permitted. If the virtual machines are in an availability zone, a standard load balancer is required. Standard load balancer requires that all VM IP addresses use standard IP addresses.
5959

60+
> [!IMPORTANT]
61+
> On September 30, 2025, the Basic SKU for the Azure Load Balancer will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer/). If you're currently using Basic Load Balancer, upgrade to Standard Load Balancer prior to the retirement date. For guidance, review [upgrade load balancer](/azure/load-balancer/load-balancer-basic-upgrade-guidance).
62+
6063
The current [Microsoft template](./availability-group-quickstart-template-configure.md) for an availability group uses a basic load balancer with basic IP addresses.
6164

6265
> [!NOTE]

0 commit comments

Comments
 (0)