Skip to content

Commit cb702a7

Browse files
rwestMSFTrwestMSFT
committed
Merge branch 'main' into rw-0610-deprecated-articles
2 parents 33c7ae3 + 59925b5 commit cb702a7

3,069 files changed

Lines changed: 36851 additions & 32056 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.

‎.openpublishing.redirection.azure-sql.json‎

Lines changed: 543 additions & 528 deletions
Large diffs are not rendered by default.

‎.openpublishing.redirection.json‎

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3657,7 +3657,7 @@
36573657
},
36583658
{
36593659
"source_path": "docs/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine.md",
3660-
"redirect_url": "https://docs.microsoft.com/troubleshoot/sql/connect/network-related-or-instance-specific-error-occurred-while-establishing-connection",
3660+
"redirect_url": "/troubleshoot/sql/connect/network-related-or-instance-specific-error-occurred-while-establishing-connection",
36613661
"redirect_document_id": false
36623662
},
36633663
{
@@ -58815,6 +58815,11 @@
5881558815
"redirect_url": "/sql/sql-server/install/planning-a-sql-server-installation",
5881658816
"redirect_document_id": false
5881758817
},
58818+
{
58819+
"source_path": "docs/sql-server/stretch-database/stretch-database-databases-and-tables-stretch-database-advisor.md",
58820+
"redirect_url": "/sql/sql-server/stretch-database/stretch-database",
58821+
"redirect_document_id": false
58822+
},
5881858823
{
5881958824
"source_path": "docs/sql-server/stretch-database/index.md",
5882058825
"redirect_url": "/sql/sql-server/stretch-database/stretch-database",
@@ -59424,6 +59429,27 @@
5942459429
"source_path": "docs/linux/tutorial-sql-server-containers-kubernetes.md",
5942559430
"redirect_url": "/sql/linux/quickstart-sql-server-containers-kubernetes",
5942659431
"redirect_document_id": true
59432+
},
59433+
{
59434+
"source_path": "docs/tools/distributed-replay/install-distributed-replay-overview.md",
59435+
"redirect_url": "/sql/tools/distributed-replay/install-distributed-replay",
59436+
"redirect_document_id": false
59437+
},
59438+
{
59439+
"source_path": "docs/tools/distributed-replay/distributed-replay-requirements.md",
59440+
"redirect_url": "/sql/tools/distributed-replay/sql-server-distributed-replay",
59441+
"redirect_document_id": false
59442+
},
59443+
{
59444+
"source_path": "docs/ssms/scripting/transact-sql-debugger-quickwatch-dialog-box.md",
59445+
"redirect_url": "/sql/ssms/scripting/transact-sql-debugger-information",
59446+
"redirect_document_id": false
59447+
},
59448+
{
59449+
"source_path": "docs/tools/sqlpackage/troubleshooting-import-export-sqlpackage.md",
59450+
"redirect_url": "/sql/tools/sqlpackage/troubleshooting-issues-and-performance-with-sqlpackage",
59451+
"redirect_document_id": false
5942759452
}
5942859453
]
5942959454
}
59455+

‎azure-sql/capacity-errors-troubleshoot.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ To register your subscription using [the Azure CLI](/cli/azure/install-azure-cli
7171

7272
```azurecli-interactive
7373
# Register the SQL resource provider to your subscription
74-
az provider register --namespace Microsoft.SqlVirtualMac
74+
az provider register --namespace Microsoft.Sql
7575
```
7676

7777
# [Azure PowerShell](#tab/powershell)

‎azure-sql/database/advance-notifications.md‎

Lines changed: 18 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Notifications can be configured so you can get texts, emails, Azure push notific
2525
> [!NOTE]
2626
> While [maintenance windows](maintenance-window.md) are generally available, advance notifications for maintenance windows are in public preview for Azure SQL Database and Azure SQL Managed Instance.
2727
28-
## Create an advance notification
28+
## Configure an advance notification
2929

3030
Advance notifications are available for Azure SQL databases that have their maintenance window configured.
3131

@@ -66,18 +66,18 @@ The following table shows the general-information notifications you may receive:
6666

6767
|Status|Description|
6868
|:---|:---|
69-
|**Planned Deployment**| Received 24 hours prior to the maintenance event. Maintenance is planned on DATE between 5pm - 8am (local time) for DB xyz.|
70-
|**In-Progress** | Maintenance for database *xyz* is starting.|
71-
|**Complete** | Maintenance of database *xyz* is complete. |
69+
|**Planned**| Received 24 hours prior to the maintenance event. Maintenance is planned on DATE between 5pm - 8am<sup>1</sup> (local time) in region *xyz*. |
70+
|**InProgress** | Maintenance for database(s) in region *xyz* is starting. |
71+
|**Complete** | Maintenance of database(s) in region *xyz* is complete. |
72+
73+
<sup>1</sup> Start and end time depend on the selected [maintenance window](maintenance-window.md).
7274

7375
The following table shows additional notifications that may be sent while maintenance is ongoing:
7476

7577
|Status|Description|
7678
|:---|:---|
77-
|**Extended** | Maintenance is in progress but didn't complete for database *xyz*. Maintenance will continue at the next maintenance window.|
78-
|**Canceled**| Maintenance for database *xyz* is canceled and will be rescheduled later. |
79-
|**Blocked**|There was a problem during maintenance for database *xyz*. We'll notify you when we resume.|
80-
|**Resumed**|The problem has been resolved and maintenance will continue at the next maintenance window.|
79+
|**Rescheduled** | 1) Maintenance is in progress but didn't complete inside maintenance window. 2) there was a problem during maintenance and it could not start. 3) Planned maintenance has started but couldn't progress to the end and will continue in next maintenance window. |
80+
|**Canceled**| Maintenance for database(s) in region *xyz* is canceled and will be rescheduled for later. |
8181

8282
## Permissions
8383

@@ -105,6 +105,16 @@ resources
105105
| project resource, status, resourceGroup, location, startTimeUtc, endTimeUtc, impactType
106106
```
107107

108+
In Azure Resource Graph (ARG) explorer you might find values for the status of deployment that are bit different than the ones displayed in the notification content.
109+
110+
|Status|Description|
111+
|:---|:---|
112+
|**Pending**| 1) Maintenance is planned on upcoming date. 2) Previously planned maintenance was rescheduled and is waiting to start in the next window. 3) Maintenance started but didn't complete in previous window and will continue in the next one. |
113+
|**InProgress** | Maintenance for resource *xyz* is starting or is in progress. |
114+
|**Completed** | Maintenance for resource *xyz* is complete. |
115+
|**NoUpdatesPending** | Previously planned maintenance for resource *xyz* is canceled and will be rescheduled for later. |
116+
|**RetryLater** | Planned maintenance for resource *xyz* has started but couldn't progress to the end and will continue in next maintenance window. |
117+
108118
For the full reference of the sample queries and how to use them across tools like PowerShell or Azure CLI, visit [Azure Resource Graph sample queries for Azure Service Health](/azure/service-health/resource-graph-samples).
109119

110120

‎azure-sql/database/audit-write-storage-account-behind-vnet-firewall.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,11 @@ For audit to write to a storage account behind a VNet or firewall, the following
4141
> * The Azure Storage account requires `Allow trusted Microsoft services to access this storage account`. Set this on the Storage Account **Firewalls and Virtual networks**.
4242
> * You must have `Microsoft.Authorization/roleAssignments/write` permission on the selected storage account. For more information, see [Azure built-in roles](/azure/role-based-access-control/built-in-roles).
4343
44+
> [!NOTE]
45+
> When Auditing to stoarge account is already enabled on a server / db, and if the target storage account is moved behind a firewall, we lose write access to
46+
the storage account and audit logs stop getting written to it.To make auditing work we have to resave the audit settings from portal.
47+
48+
4449
## Configure in Azure portal
4550

4651
Connect to [Azure portal](https://portal.azure.com) with your subscription. Navigate to the resource group and server.

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,12 +37,13 @@ You can use SQL Database auditing to:
3737
- **Analyze** reports. You can find suspicious events, unusual activity, and trends.
3838

3939
> [!IMPORTANT]
40-
> Auditing for Azure SQL Database, Azure Synapse and Azure SQL Managed Instance is optimized for availability and performance. During very high activity, or high network load, Azure SQL Database, Azure Synapse and Azure SQL Managed Instance allow operations to proceed and may not record some audited events.
40+
> Auditing for Azure SQL Database, Azure Synapse and Azure SQL Managed Instance is optimized for availability and performance of the database(s) or instance(s) that are being audited. During periods of very high activity or high network load, the auditing feature may allow transactions to proceed without recording all of the events marked for auditing.
4141
4242
### Auditing limitations
4343

44-
- **Premium storage** is currently **not supported**.
45-
- **Hierarchical namespace** for **Azure Data Lake Storage Gen2 storage account** is currently **not supported**.
44+
- **Premium storage** with **BlockBlobStorage** is supported.
45+
- **User managed identity** authentication type for enabling auditing to **storage** is not yet supported.
46+
- **Hierarchical namespace** for all types of **standard storage account** and **premium storage account with BlockBlobStorage** is supported.
4647
- Enabling auditing on a paused **Azure Synapse** is not supported. To enable auditing, resume Azure Synapse.
4748
- Auditing for **Azure Synapse SQL pools** supports default audit action groups **only**.
4849
- When you configure the auditing in Azure SQL Server or Azure SQL Database with log destination as the storage account, the target storage account must be enabled with access to storage account keys. If the storage account is configured to use Azure AD authentication only and not configured for access key usage, the auditing cannot be configured. <!-- REST API reference: - https://docs.microsoft.com/rest/api/sql/2021-08-01-preview/server-blob-auditing-policies/create-or-update -->

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ In this tutorial, you learn how to:
103103
104104
## Grant server-level roles to Azure AD logins
105105

106-
You can add logins to the [built-in server-level roles](security-server-roles.md#built-in-server-level-roles), such as the **##MS_DefinitionReader##**, **##MS_ServerStateReader##**, or **##MS_ServerStateManager##** role.
106+
You can add logins to the [fixed server-level roles](security-server-roles.md#fixed-server-level-roles), such as the **##MS_DefinitionReader##**, **##MS_ServerStateReader##**, or **##MS_ServerStateManager##** role.
107107

108108
> [!NOTE]
109109
> The server-level roles mentioned here are not supported for Azure AD groups.

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The [SQL Security Manager](/azure/role-based-access-control/built-in-roles#sql-s
3535

3636
The following section provides you with examples and scripts on how to create a logical server or managed instance with an Azure AD admin set for the server or instance, and have Azure AD-only authentication enabled during server creation. For more information on the feature, see [Azure AD-only authentication](authentication-azure-ad-only-authentication.md).
3737

38-
In our examples, we're enabling Azure AD-only authentication during server or managed instance creation, with a system assigned server admin and password. This will prevent server admin access when Azure AD-only authentication is enabled, and only allows the Azure AD 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 Azure AD-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.
38+
In our examples, we're enabling Azure AD-only authentication during server or managed instance creation, with a system assigned server admin and password. This will prevent server admin access when Azure AD-only authentication is enabled, and only allows the Azure AD 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 Azure AD-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.
3939

4040
> [!NOTE]
4141
> To change the existing properties after server or managed instance creation, other existing APIs should be used. For more information, see [Managing Azure AD-only authentication using APIs](authentication-azure-ad-only-authentication.md#managing-azure-ad-only-authentication-using-apis) and [Configure and manage Azure AD authentication with Azure SQL](authentication-aad-configure.md).
@@ -367,7 +367,7 @@ Replace the following values in the example:
367367

368368

369369
```powershell
370-
New-AzSqlInstance -Name "<managedinstancename>" -ResourceGroupName "<ResourceGroupName>" -ExternalAdminName "<AzureADAccount>" -EnableActiveDirectoryOnlyAuthentication -Location "<Location>" -SubnetId "/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Network/virtualNetworks/<VNetName>/subnets/<SubnetName>" -LicenseType LicenseIncluded -StorageSizeInGB 1024 -VCore 16 -Edition "GeneralPurpose" -ComputeGeneration Gen4
370+
New-AzSqlInstance -Name "<managedinstancename>" -ResourceGroupName "<ResourceGroupName>" -ExternalAdminName "<AzureADAccount>" -EnableActiveDirectoryOnlyAuthentication -Location "<Location>" -SubnetId "/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Network/virtualNetworks/<VNetName>/subnets/<SubnetName>" -LicenseType LicenseIncluded -StorageSizeInGB 128 -VCore 4 -Edition "GeneralPurpose" -ComputeGeneration Gen5
371371
```
372372

373373
For more information, see [New-AzSqlInstance](/powershell/module/az.sql/new-azsqlinstance).

‎azure-sql/database/authentication-azure-ad-user-assigned-managed-identity-create-server.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,15 @@ ms.topic: conceptual
88
author: GithubMirek
99
ms.author: mireks
1010
ms.reviewer: vanto
11-
ms.date: 12/15/2021
11+
ms.date: 06/30/2022
1212
---
1313

1414
# Create an Azure SQL Database server with a user-assigned managed identity
1515

1616
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
1717

1818
> [!NOTE]
19-
> User-assigned managed identity for Azure SQL is in **public preview**. If you're looking for a guide on Azure SQL Managed Instance, see [Create an Azure SQL Managed Instance with a user-assigned managed identity](../managed-instance/authentication-azure-ad-user-assigned-managed-identity-create-managed-instance.md).
19+
> If you're looking for a guide on Azure SQL Managed Instance, see [Create an Azure SQL Managed Instance with a user-assigned managed identity](../managed-instance/authentication-azure-ad-user-assigned-managed-identity-create-managed-instance.md).
2020
2121
This how-to guide outlines the steps to create a [logical server](logical-servers.md) for Azure SQL Database with a [user-assigned managed identity](/azure/active-directory/managed-identities-azure-resources/overview#managed-identity-types). For more information on the benefits of using a user-assigned managed identity for the server identity in Azure SQL Database, see [User-assigned managed identity in Azure AD for Azure SQL](authentication-azure-ad-user-assigned-managed-identity.md).
2222

@@ -65,13 +65,13 @@ The following steps outline the process of creating a new Azure SQL Database log
6565

6666
11. Select **Next: Security** at the bottom of the page.
6767

68-
12. On the Security tab, under **Identity (preview)**, select **Configure Identities**.
68+
12. On the Security tab, under **Identity**, select **Configure Identities**.
6969

70-
:::image type="content" source="media/authentication-azure-ad-user-assigned-managed-identity/create-server-configure-identities.png" alt-text="Screenshot of Azure portal security settings of the create database process":::
70+
:::image type="content" source="media/authentication-azure-ad-user-assigned-managed-identity/create-server-configure-identities.png" alt-text="Screenshot of Azure portal security settings of the create database process.":::
7171

72-
13. On the **Identity (preview)** blade, under **User assigned managed identity**, select **Add**. Select the desired **Subscription** and then under **User assigned managed identities** select the desired user assigned managed identity from the selected subscription. Then select the **Select** button.
72+
13. On the **Identity** blade, under **User assigned managed identity**, select **Add**. Select the desired **Subscription** and then under **User assigned managed identities** select the desired user assigned managed identity from the selected subscription. Then select the **Select** button.
7373

74-
:::image type="content" source="media/authentication-azure-ad-user-assigned-managed-identity/user-assigned-managed-identity-configuration.png" alt-text="Azure portal screenshot of adding user assigned managed identity when configuring server identity":::
74+
:::image type="content" source="media/authentication-azure-ad-user-assigned-managed-identity/user-assigned-managed-identity-configuration.png" alt-text="Azure portal screenshot of adding user assigned managed identity when configuring server identity.":::
7575

7676
:::image type="content" source="media/authentication-azure-ad-user-assigned-managed-identity/select-a-user-assigned-managed-identity.png" alt-text="Azure portal screenshot of user assigned managed identity when configuring server identity":::
7777

0 commit comments

Comments
 (0)