Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into 20230223-arcee-features-by-os-type

Author: Mike Ray (Microsoft)

.openpublishing.redirection.json

@@ -59643,6 +59643,21 @@
       "source_path": "azure-sql/database/sql-azure-vulnerability-assessment-storage.md",
       "redirect_url": "azure-sql/database/sql-database-vulnerability-assessment-storage",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/linux/sql-server-linux-release-history-2017.md",
+      "redirect_url": "/troubleshoot/sql/linux/release-history-2017?toc=/sql/toc.json&bc=/sql/breadcrumb/toc.json",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/linux/sql-server-linux-release-history-2019.md",
+      "redirect_url": "/troubleshoot/sql/linux/release-history-2019?toc=/sql/toc.json&bc=/sql/breadcrumb/toc.json",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/linux/sql-server-linux-release-history-2022.md",
+      "redirect_url": "/troubleshoot/sql/linux/release-history-2022?toc=/sql/toc.json&bc=/sql/breadcrumb/toc.json",
+      "redirect_document_id": false
     }
   ]
 }

azure-sql/database/analyze-prevent-deadlocks.md

@@ -814,6 +814,6 @@ Learn more about performance in Azure SQL Database:
 - [Understand and resolve Azure SQL Database blocking problems](understand-resolve-blocking.md)
 - [Transaction Locking and Row Versioning Guide](/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide)
 - [SET TRANSACTION ISOLATION LEVEL](/sql/t-sql/statements/set-transaction-isolation-level-transact-sql)
-- [Azure SQL Database: Improving Performance Tuning with Automatic Tuning](/Shows/Data-Exposed/Azure-SQL-Database-Improving-Performance-Tuning-with-Automatic-Tuning)
+- [Azure SQL Database: improving performance tuning with automatic tuning](/Shows/Data-Exposed/Azure-SQL-Database-Improving-Performance-Tuning-with-Automatic-Tuning)
 - [Deliver consistent performance with Azure SQL](/training/modules/azure-sql-performance/)
 - [Retry logic for transient errors](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors).

azure-sql/database/arm-templates-content-guide.md

@@ -1,8 +1,8 @@
 ---
-title: Azure Resource Manager templates - Azure SQL Database & SQL Managed Instance
+title: Azure Resource Manager templates
 description: Use Azure Resource Manager templates to create and configure Azure SQL Database and Azure SQL Managed Instance.
-author: srdan-bozovic-msft
-ms.author: srbozovi
+author: urosmil
+ms.author: urmilano
 ms.reviewer: wiassaf, mathoma
 ms.date: 06/30/2021
 ms.service: sql-db-mi

azure-sql/database/connectivity-settings.md

@@ -118,7 +118,7 @@ Currently, we support TLS 1.0, 1.1, and 1.2. Setting a minimal TLS version ensur
 > [!IMPORTANT]
 > The default for the minimal TLS version is to allow all versions. After you enforce a version of TLS, it's not possible to revert to the default.
 
-For customers with applications that rely on older versions of TLS, we recommend setting the minimal TLS version according to the requirements of your applications. For customers that rely on applications to connect by using an unencrypted connection, we recommend not setting any minimal TLS version.
+For customers with applications that rely on older versions of TLS, we recommend setting the minimal TLS version according to the requirements of your applications. If application requirements are unknown or workloads rely on older drivers that are no longer maintained, we recommend not setting any minimal TLS version.
 
 For more information, see [TLS considerations for SQL Database connectivity](connect-query-content-reference-guide.md#tls-considerations-for-database-connectivity).
 

azure-sql/database/elastic-query-overview.md

@@ -137,7 +137,7 @@ Elastic query is included in the cost of Azure SQL Database. Note that topologie
 * Import/Export for SQL Database does not yet support external data sources and external tables. If you need to use Import/Export, drop these objects before exporting and then re-create them after importing.
 * Elastic query currently only supports read-only access to external tables. You can, however, use full Transact-SQL functionality on the database where the external table is defined. This can be useful to, e.g., persist temporary results using, for example, SELECT <column_list> INTO <local_table>, or to define stored procedures on the elastic query database that refer to external tables.
 * Except for nvarchar(max), LOB types (including spatial types) are not supported in external table definitions. As a workaround, you can create a view on the remote database that casts the LOB type into nvarchar(max), define your external table over the view instead of the base table and then cast it back into the original LOB type in your queries.
-* Columns of nvarchar(max) data type in result set disable advanced batching technics used in Elastic Query implementation and may affect performance of query for an order of magnitude, or even two orders of magnitude in non-canonical use cases where large amount of non-aggregated data is being transferred as a result of query.
+* Columns of nvarchar(max) data type in result set disable advanced batching techniques used in Elastic Query implementation and may affect performance of query for an order of magnitude, or even two orders of magnitude in non-canonical use cases where large amount of non-aggregated data is being transferred as a result of query.
 * Column statistics over external tables are currently not supported. Table statistics are supported, but need to be created manually.
 * Cursors are not supported for external tables in Azure SQL Database.
 * Elastic query works with Azure SQL Database only. You cannot use it for querying a SQL Server instance.

azure-sql/database/high-availability-sla.md

@@ -90,7 +90,7 @@ The zone-redundant version of the high availability architecture is illustrated
 
 Consider the following when using zone redundancy: 
 
-- This feature is currently in preview for SQL Managed Instance, and only available on the Business Critical service tier, and on Gen5 hardware. In SQL Database, when using the Business Critical tier, zone-redundant configuration is only available when the Gen5 hardware is selected. 
+- This feature is currently in preview for SQL Managed Instance, and only available on the Business Critical service tier. In SQL Database, when using the Business Critical tier, zone-redundant configuration is only available when the Gen5 hardware is selected. 
 - For up to date information about the regions that support zone-redundant databases, see [Services support by region](/azure/availability-zones/az-region).
 - For zone redundant availability, choosing a [maintenance window](./maintenance-window.md) other than the default is currently available in [select regions](maintenance-window.md#azure-region-support).
 

azure-sql/database/index.yml

@@ -150,7 +150,7 @@ landingContent:
       - linkListType: reference
         links:
           - text: Migration guide
-            url: https://datamigration.microsoft.com/
+            url: /data-migration/
           - text: Transact-SQL (T-SQL)
             url: /sql/t-sql/language-reference
           - text: Azure CLI

azure-sql/database/media/transparent-data-encryption-byok-key-rotation/auto-rotate-key-primary.png

@@ -41,7 +41,7 @@ The Hyperscale service tier in Azure SQL Database provides the following additio
 
 The Hyperscale service tier removes many of the practical limits traditionally seen in cloud databases. Where most other databases are limited by the resources available in a single node, databases in the Hyperscale service tier have no such limits. With its flexible storage architecture, storage grows as needed. In fact, Hyperscale databases aren't created with a defined max size. A Hyperscale database grows as needed - and you're billed only for the capacity you use. For read-intensive workloads, the Hyperscale service tier provides rapid scale-out by provisioning additional replicas as needed for offloading read workloads.
 
-Additionally, the time required to create database backups or to scale up or down is no longer tied to the volume of data in the database. Hyperscale databases are backed up virtually instantaneously. You can also scale a database in the tens of terabytes up or down within minutes in the provisioned compute tier or use [serverless] (serverless-tier-overview.md) to scale compute automatically. This capability frees you from concerns about being boxed in by your initial configuration choices.
+Additionally, the time required to create database backups or to scale up or down is no longer tied to the volume of data in the database. Hyperscale databases are backed up virtually instantaneously. You can also scale a database in the tens of terabytes up or down within minutes in the provisioned compute tier or use [serverless](serverless-tier-overview.md) to scale compute automatically. This capability frees you from concerns about being boxed in by your initial configuration choices.
 
 For more information about the compute sizes for the Hyperscale service tier, see [Service tier characteristics](service-tiers-vcore.md#service-tiers).