Merge branch 'release-dallas' of https://github.com/MicrosoftDocs/sql-docs-pr into 2022ledger

Author: VanMSFT

.openpublishing.redirection.azure-sql.json

@@ -41190,6 +41190,11 @@
       "redirect_url": "/sql/big-data-cluster/view-cluster-status#big-data-clusters-troubleshooting-resources",
       "redirect_document_id": true
     },
+    {
+      "source_path": "docs/big-data-cluster/release-notes-cumulative-update-16.md",
+      "redirect_url": "/sql/big-data-cluster/release-notes-big-data-cluster",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/big-data-cluster/configure-cluster.md",
       "redirect_url": "/sql/big-data-cluster/configure-bdc-overview",

.openpublishing.redirection.json

@@ -22,7 +22,9 @@ Changing to Azure Hybrid Benefit does not require any downtime.
 
 ## Overview
 
-![vcore pricing structure](./media/azure-hybrid-benefit/pricing.png)
+:::image type="complex" source="media/azure-hybrid-benefit/pricing.png" alt-text="Diagram of vCore pricing structure for SQL Database.":::
+Diagram of vCore pricing structure for SQL Database. 'License Included' pricing is made up of base compute and SQL license components. Azure Hybrid Benefit pricing is made up of base compute and software assurance components.
+:::image-end:::
 
 With Azure Hybrid Benefit, you pay only for the underlying Azure infrastructure by using your existing SQL Server license for the SQL Server database engine itself (Base Compute pricing). If you do not use Azure Hybrid Benefit, you pay for both the underlying infrastructure and the SQL Server license (License-Included pricing).
 

azure-sql/azure-hybrid-benefit.md

@@ -6,8 +6,8 @@ ms.service: sql-database
 ms.subservice: high-availability
 ms.custom: sqldbrb=1, devx-track-azurecli
 ms.topic: tutorial
-author: emlisa
-ms.author: emlisa
+author: rajeshsetlem
+ms.author: rsetlem
 ms.reviewer: kendralittle, mathoma
 ms.date: 08/20/2021
 ---

azure-sql/database/active-geo-replication-configure-portal.md

@@ -5,8 +5,8 @@ ms.service: sql-database
 ms.subservice: high-availability
 ms.custom: sqldbrb=1
 ms.topic: conceptual
-author: emlisa
-ms.author: emlisa
+author: rajeshsetlem
+ms.author: rsetlem
 ms.reviewer: kendralittle, mathoma
 ms.date: 4/14/2022
 ---
@@ -36,7 +36,7 @@ If your application requires a stable connection endpoint and automatic geo-fail
 
 The following diagram illustrates a typical configuration of a geo-redundant cloud application using Active geo-replication.
 
-![active geo-replication](./media/active-geo-replication-overview/geo-replication.png)
+![active geo-replication](./media/active-geo-replication-overview/geo-replication-updated.png)
 
 If for any reason your primary database fails, you can initiate a geo-failover to any of your secondary databases. When a secondary is promoted to the primary role, all other secondaries are automatically linked to the new primary.
 
@@ -197,7 +197,7 @@ To create a geo-secondary in a subscription different from the subscription of t
 10. After the geo-secondary is successfully created, the users, logins, and firewall rules created by this procedure can be removed.
 
 > [!NOTE]
-> Cross-subscription geo-replication operations including setup and geo-failover are only supported using T-SQL commands.
+> Cross-subscription geo-replication operations including setup and geo-failover are only supported using REST API & T-SQL commands.
 > 
 > Adding a geo-secondary using T-SQL is not supported when connecting to the primary server over a [private endpoint](private-endpoint-overview.md). If a private endpoint is configured but public network access is allowed, adding a geo-secondary is supported when connected to the primary server from a public IP address. Once a geo-secondary is added, public access can be [denied](connectivity-settings.md#deny-public-network-access).
 > 

azure-sql/database/active-geo-replication-overview.md

@@ -7,8 +7,8 @@ ms.subservice: high-availability
 ms.custom: sqldbrb=1
 ms.devlang: 
 ms.topic: how-to
-author: emlisa
-ms.author: emlisa
+author: rajeshsetlem
+ms.author: rsetlem
 ms.reviewer: kendralittle, mathoma, vanto
 ms.date: 12/18/2018
 ---

azure-sql/database/active-geo-replication-security-configure.md

@@ -6,8 +6,8 @@ ms.service: sql-database
 ms.subservice: high-availability
 ms.custom: sql-db-mi-split
 ms.topic: conceptual
-author: emlisa
-ms.author: emlisa
+author: rajeshsetlem
+ms.author: rsetlem
 ms.reviewer: kendralittle, mathoma
 ms.date: 03/01/2022
 ---

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

@@ -494,7 +494,7 @@ Backup and restore operations for Hyperscale databases are fast regardless of da
 
 ### Hyperscale backup retention
 
-Hyperscale supports short-term backup retention (STR) of 7 days by default; long-term retention (LTR) policies aren't currently supported.
+Default short-term backup retention (STR) for Hyperscale databases is 7 days; long-term retention (LTR) policies aren't currently supported.
 
 > [!NOTE]
 > Short-term backup retention up to 35 days for Hyperscale databases is now in preview. 
@@ -538,7 +538,7 @@ To view backup and data storage metrics in the Azure portal, follow these steps:
 Backup storage consumption for a Hyperscale database depends on the retention period, choice of region, backup storage redundancy and workload type. Consider some of the following tuning techniques to reduce your backup storage consumption for a Hyperscale database:
 
 - Reduce the [backup retention period](#change-the-short-term-retention-policy-using-the-azure-portal) to the minimum possible for your needs.
-- Avoid doing large write-operations, such as index maintenance, more frequently than you need to. For index maintenance recommendations, see [Optimize index maintenance to improve query performance and reduce resource consumption](/sql/relational-databases/indexes/reorganize-and-rebuild-indexes.md).
+- Avoid doing large write-operations, such as index maintenance, more frequently than you need to. For index maintenance recommendations, see [Optimize index maintenance to improve query performance and reduce resource consumption](/sql/relational-databases/indexes/reorganize-and-rebuild-indexes).
 - For large data-load operations, consider using data compression when appropriate.
 - Use the `tempdb` database instead of permanent tables in your application logic to store temporary results and/or transient data.
 - Use locally-redundant or zone-redundant backup storage when geo-restore capability is unnecessary (for example: dev/test environments). 
@@ -572,9 +572,6 @@ Backup storage redundancy for databases in Azure SQL Database can be configured
 
 For Azure SQL Managed Instance, backup storage redundancy is set at the instance level, and it is applied for all belonging managed databases. It can be configured at the time of an instance creation or updated for existing instances; the backup storage redundancy change would trigger then a new full backup per database and the change will apply for all future backups. The default storage redundancy type is geo-redundancy (RA-GRS).
 
-> [!NOTE]
-> Backup storage redundancy change for SQL Managed Instance is currently available only for the Public cloud via Azure Portal.
-
 ### Configure backup storage redundancy by using the Azure portal
 
 #### [SQL Database](#tab/single-database)

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

@@ -9,8 +9,8 @@ ms.subservice: high-availability
 ms.custom: sqldbrb=2
 ms.devlang: 
 ms.topic: conceptual
-author: emlisa
-ms.author: emlisa
+author: rajeshsetlem
+ms.author: rsetlem
 ms.reviewer: kendralittle, mathoma
 ms.date: 10/18/2021
 monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"

azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview.md

@@ -11,13 +11,13 @@ ms.topic: quickstart
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: kendralittle, mathoma
-ms.date: 04/14/2021
+ms.date: 05/05/2022
 monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"
 ---
 # Quickstart: Use Golang to query a database in Azure SQL Database or Azure SQL Managed Instance
 [!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
-In this quickstart, you'll use the [Golang](https://godoc.org/github.com/denisenkom/go-mssqldb) programming language to connect to a database in Azure SQL Database or Azure SQL Managed Instance. You'll then run Transact-SQL statements to query and modify data. [Golang](https://go.dev/) is an open-source programming language that makes it easy to build simple, reliable, and efficient software.  
+In this quickstart, you'll use the Golang programming language to connect to a database in Azure SQL Database or Azure SQL Managed Instance with the [go-mssqldb]((https://github.com/microsoft/go-mssqldb). The sample queries and modifies data with explicit Transact-SQL statements. [Golang](https://go.dev/) is an open-source programming language that makes it easy to build simple, reliable, and efficient software.  
 
 ## Prerequisites
 
@@ -70,7 +70,7 @@ Get the connection information you need to connect to the database. You'll need
 
    ```bash
    cd SqlServerSample
-   go get github.com/denisenkom/go-mssqldb
+   go get github.com/microsoft/go-mssqldb
    ```
 
 ## Create sample data
@@ -114,7 +114,7 @@ Get the connection information you need to connect to the database. You'll need
    package main
 
    import (
-       _ "github.com/denisenkom/go-mssqldb"
+       _ "github.com/microsoft/go-mssqldb"
        "database/sql"
        "context"
        "log"
@@ -330,5 +330,5 @@ Get the connection information you need to connect to the database. You'll need
 ## Next steps
 
 - [Design your first database in Azure SQL Database](design-first-database-tutorial.md)
-- [Golang driver for SQL Server](https://github.com/denisenkom/go-mssqldb)
-- [Report issues or ask questions](https://github.com/denisenkom/go-mssqldb/issues)
+- [Golang driver for SQL Server](https://github.com/microsoft/go-mssqldb)
+- [Report issues or ask questions](https://github.com/microsoft/go-mssqldb/issues)