Merge branch 'main' into alexbuckgit/docutune-autopr-docs-link-absolute-20220912-194103-0788764

Author: alexbuckgit

.openpublishing.redirection.azure-sql.json

@@ -539,6 +539,16 @@
       "source_path_from_root": "/azure-sql/database/predictive-model-build-compare-tutorial.md",
       "redirect_url": "/sql/machine-learning/tutorials/r-predictive-model-train?context=/azure/azure-sql/managed-instance/context/ml-context&view=azuresqldb-mi-current",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/azure-sql/managed-instance/custom-dns-configure.md",
+      "redirect_url": "/azure/azure-sql/managed-instance/resolve-private-domain-names",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/azure-sql/managed-instance/synchronize-vnet-dns-servers-setting-on-virtual-cluster.md",
+      "redirect_url": "/azure/azure-sql/managed-instance/resolve-private-domain-names",
+      "redirect_document_id": false
     }
   ]
 }

.openpublishing.redirection.json

@@ -59454,6 +59454,16 @@
       "source_path": "docs/tools/sqlpackage/troubleshooting-import-export-sqlpackage.md",
       "redirect_url": "/sql/tools/sqlpackage/troubleshooting-issues-and-performance-with-sqlpackage",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/sql-server/partner-big-data-cluster.md",
+      "redirect_url": "/sql/big-data-cluster/partner-big-data-cluster",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "azure-sql/database/ledger-digest-management-and-database-verification.md",
+      "redirect_url": "/sql/relational-databases/security/ledger/ledger-digest-management",
+      "redirect_document_id": false
     }
   ]
 }

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

@@ -39,6 +39,7 @@ For audit to write to a storage account behind a VNet or firewall, the following
 > * The storage account must be on the same tenant and at the same location as the [logical SQL server](logical-servers.md) (it's OK to be on different subscriptions).
 > * The Azure Storage account requires `Allow trusted Microsoft services to access this storage account`. Set this on the Storage Account **Firewalls and Virtual networks**.
 > * 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).
+> * **User managed identity authentication** type for enabling auditing to storage behind firewall is not currently supported.
 
 > [!NOTE]
 > 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 

azure-sql/database/auto-failover-group-configure-sql-db.md

@@ -107,6 +107,9 @@ Create your failover group and add your database to it using PowerShell.
    Write-host "Successfully added the database to the failover group..."
    ```
 
+> [!NOTE]
+> It's possible to deploy your auto-failover group across subscriptions by using the `-PartnerSubscriptionId` parameter in Azure Powershell starting with [Az.SQL 3.11.0](https://www.powershellgallery.com/packages/Az.Sql/3.11.0). To learn more, review the following [Example](/powershell/module/az.sql/new-azsqldatabasefailovergroup#example-3). 
+
 ---
 
 ## Test failover

azure-sql/database/automated-backups-overview.md

@@ -211,15 +211,12 @@ If you delete a database, the system keeps backups in the same way that it would
 
 For SQL Database, you can configure full LTR backups for up to 10 years in Azure Blob Storage. After the LTR policy is configured, full backups are automatically copied to a different storage container weekly. 
 
-To meet various compliance requirements, you can select different retention periods for weekly, monthly, and/or yearly full backups. The frequency depends on the policy. For example, setting `W=0, M=1` would create an LTR copy monthly. For more information about LTR, see [Long-term retention](long-term-retention-overview.md).  
+To meet various compliance requirements, you can select different retention periods for weekly, monthly, and/or yearly full backups. The frequency depends on the policy. For example, setting `W=0, M=1` would create an LTR copy monthly. For more information about LTR, see [Long-term retention](long-term-retention-overview.md). Databases in the Hyperscale service tier don't currently support long-term retention.
 
 Updating the backup storage redundancy for an existing database applies the change only to subsequent backups taken in the future and not for existing backups. All existing LTR backups for the database will continue to reside in the existing storage blob. New backups will be replicated based on the configured backup storage redundancy. 
 
 Storage consumption depends on the selected frequency and retention periods of LTR backups. You can use the [LTR pricing calculator](https://azure.microsoft.com/pricing/calculator/?service=sql-database) to estimate the cost of LTR storage.
 
-> [!NOTE]
-> Long-term retention for Hyperscale databases is currently in preview.
-
 ## Backup storage costs
 
 The price for backup storage varies and depends on your [purchasing model (DTU or vCore)](purchasing-models.md), chosen backup storage redundancy option, and region. Backup storage is charged based on gigabytes consumed per month, at the same rate for all backups. 

azure-sql/database/data-discovery-and-classification-overview.md

@@ -5,7 +5,7 @@ description: Data Discovery & Classification for Azure SQL Database, Azure SQL M
 author: Madhumitatripathy
 ms.author: matripathy
 ms.reviewer: wiassaf, vanto, mathoma
-ms.date: 05/02/2022
+ms.date: 09/14/2022
 ms.service: sql-db-mi
 ms.subservice: security
 ms.topic: conceptual
@@ -116,7 +116,8 @@ Microsoft Information Protection (MIP) labels provide a simple and uniform way f
 
 #### Prerequisites to switch to MIP policy
 
-- The current user has tenant wide security admin permissions to apply policy at the tenant root management group level. For more information, see [Grant tenant-wide permissions to yourself](/azure/defender-for-cloud/tenant-wide-permissions-management#grant-tenant-wide-permissions-to-yourself).
+- The current user has tenant wide **Security Admin** permissions to apply policy at the tenant root management group level. For more information, see [Grant tenant-wide permissions to yourself](/azure/defender-for-cloud/tenant-wide-permissions-management#grant-tenant-wide-permissions-to-yourself).
+  :::image type="content" source="media/data-discovery-and-classification-overview/request-security-admin-permissions.png" alt-text="Screenshot of Azure portal request for tenant level Security Admin permissions.":::
 - Your tenant has an active Microsoft 365 subscription and you have labels published for the current user. For more information, see [Create and configure sensitivity labels and their policies](/microsoft-365/compliance/create-sensitivity-labels).
 
 ### Classify database in Microsoft Information Protection policy mode

azure-sql/database/dns-alias-overview.md

@@ -18,7 +18,7 @@ Azure SQL Database has a Domain Name System (DNS) server. PowerShell and REST AP
 A *DNS alias* can be used in place of the server name. Client programs can use the alias in their connection strings. The DNS alias provides a translation layer that can redirect your client programs to different servers. This layer spares you the difficulties of having to find and edit all the clients and their connection strings.
 
 > [!NOTE]
-> In Azure Synapse Analytics, the Azure SQL logical server DNS alias is only supported for dedicated SQL Pool (formerly DW). For dedicated SQL pools in Azure Synapse workspaces, the DNS alias is not currently supported.
+> In Azure Synapse Analytics, the Azure SQL logical server DNS alias is only supported for dedicated SQL Pool (formerly DW). For dedicated SQL pools in Azure Synapse workspaces, the DNS alias is not currently supported. [What's the difference?](https://aka.ms/dedicatedSQLpooldiff)
 
 Common uses for a DNS alias include the following cases:
 
@@ -114,4 +114,4 @@ Presently, a DNS alias has the following limitations:
 
 ## Next steps
 
-- [PowerShell for DNS Alias to Azure SQL Database](dns-alias-powershell-create.md)
+- [PowerShell for DNS Alias to Azure SQL Database](dns-alias-powershell-create.md)

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -42,8 +42,7 @@ The following table lists the features of Azure SQL Database that are currently
 | [SQL Database emulator](local-dev-experience-sql-database-emulator.md) | The Azure SQL Database emulator provides the ability to locally validate database and query design together with client application code in a simple and frictionless model as part of the application development process. | 
 | [SQL Database Projects extension](/sql/azure-data-studio/extensions/sql-database-project-extension) | An extension to develop databases for Azure SQL Database with Azure Data Studio and VS Code. A SQL project is a local representation of SQL objects that comprise the schema for a single database, such as tables, stored procedures, or functions. | 
 | [SQL Insights](/azure/azure-monitor/insights/sql-insights-overview) | SQL Insights (preview) is a comprehensive solution for monitoring any product in the Azure SQL family. SQL Insights (preview) uses dynamic management views to expose the data you need to monitor health, diagnose problems, and tune performance.|
-| [Azure SQL Database Hyperscale tier long-term retention](long-term-retention-overview.md) | Long-term retention (LTR) capability for Hyperscale databases is now in preview. | 
-
+| [UMI for auditing](auditing-overview.md) | Configure the storage account for your SQL auditing logs by using User Managed Identity (UMI). | 
 
 ## General availability (GA)
 
@@ -73,13 +72,16 @@ Learn about significant changes to the Azure SQL Database documentation.
 
 | Changes | Details |
 | --- | --- |
-| [Azure SQL Database Hyperscale tier long-term retention](long-term-retention-overview.md) | Long-term retention (LTR) capability for Hyperscale databases is now in preview. | 
+| **Cross-subscription failover group with Azure PowerShell** | It's now possible to deploy your auto-failover group for a single database across subscriptions by using Azure PowerShell. To learn more, review [Configure auto-failover group](auto-failover-group-configure-sql-db.md?view=azuresql&tabs=azure-powershell&pivots=azure-sql-single-db&preserve-view=true#create-failover-group). |
+| **UMI support for auditing preview** | It's now possible to configure the storage account used for SQL auditing logs by using User Managed Identity (UMI). This feature is currently in preview. Review [auditing](auditing-overview.md) to learn more. |
+
 
 ### August 2022
 
 | Changes | Details |
 | --- | --- |
-| **Zone redundant configuration for Hyperscale databases** | The zone redundant configuration feature utilizes [Azure Availability Zones](/azure/availability-zones/az-overview#availability-zones) to replicate databases across multiple physical locations within an Azure region. By selecting [zone redundancy](high-availability-sla.md#hyperscale-service-tier-zone-redundant-availability), you can make your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. This configuration option is now generally available. To learn more, review  [Zone redundant configuration for Hyperscale databases](high-availability-sla.md#hyperscale-service-tier-zone-redundant-availability). |
+| **Zone redundant configuration for Hyperscale databases GA** | The zone redundant configuration feature utilizes [Azure Availability Zones](/azure/availability-zones/az-overview#availability-zones) to replicate databases across multiple physical locations within an Azure region. By selecting [zone redundancy](high-availability-sla.md#hyperscale-service-tier-zone-redundant-availability), you can make your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. This configuration option is now generally available. To learn more, review  [Zone redundant configuration for Hyperscale databases](high-availability-sla.md#hyperscale-service-tier-zone-redundant-availability). |
+| **Query Store hints GA** | You can use query hints to optimize your query execution via the OPTION clause. This feature is now generally available for Azure SQL Database. To learn more, review [Query Store hints](/sql/relational-databases/performance/query-store-hints?view=azuresqldb-current&preserve-view=true). |
 
 ### June 2022
 

azure-sql/database/elastic-query-vertical-partitioning.md

@@ -109,7 +109,10 @@ CREATE EXTERNAL TABLE [dbo].[customer]
       [c_lastname] nvarchar(256) NOT NULL,
       [street] nvarchar(256) NOT NULL,
       [city] nvarchar(256) NOT NULL,
-      [state] nvarchar(20) NULL,
+      [state] nvarchar(20) NULL
+   )
+   WITH
+   (
       DATA_SOURCE = RemoteReferenceData
    );
 ```

azure-sql/database/hyperscale-automated-backups-overview.md

@@ -42,11 +42,10 @@ Creation of new databases by restoring an existing backup or copying the databas
 
 ## Backup retention
 
-Default short-term retention of backups for Hyperscale databases is 7 days. 
+Default short-term retention of backups for Hyperscale databases is 7 days. Long-term retention (LTR) policies aren't currently supported.
 
 > [!NOTE]
 > - Short-term retention of backups in the range of 1 to 35 days for Hyperscale databases is now in preview.
-> - Long-term retention (LTR) capability for Hyperscale databases is now in preview.
 
 ## Backup scheduling