Merge branch 'main' into rw-0901-includes-linux

Author: rwestMSFT

.openpublishing.redirection.json

@@ -41280,6 +41280,11 @@
       "redirect_url": "/sql/sql-server/",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/relational-databases/integrated-acceleration/intel-quickassist.md",
+      "redirect_url": "/sql/relational-databases/integrated-acceleration/use-integrated-acceleration-and-offloading",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/relational-databases/system-catalog-views/sys-sql-feature-restrictions.md",
       "redirect_url": "/sql/sql-server/what-s-new-in-sql-server-ver15",

azure-sql/database/service-tier-hyperscale.md

@@ -149,7 +149,7 @@ These are the current limitations of the Hyperscale service tier.  We're activel
 | Service tier change from Hyperscale to General Purpose tier is supported directly under limited scenarios | Reverse migration from Hyperscale allows customers who have recently migrated an existing Azure SQL Database to the Hyperscale service tier to move to General Purpose tier, should Hyperscale not meet their needs. While reverse migration is initiated by a service tier change, it's essentially a size-of-data move between different architectures. Databases created in the Hyperscale service tier aren't eligible for reverse migration. Learn the [limitations for reverse migration](manage-hyperscale-database.md#limitations-for-reverse-migration). <BR/><BR/> For databases that don't qualify for reverse migration, the only way to migrate from Hyperscale to a non-Hyperscale service tier is to export/import using a bacpac file or other data movement technologies (Bulk Copy, Azure Data Factory, Azure Databricks, SSIS, etc.) Bacpac export/import from Azure portal, from PowerShell using [New-AzSqlDatabaseExport](/powershell/module/az.sql/new-azsqldatabaseexport) or [New-AzSqlDatabaseImport](/powershell/module/az.sql/new-azsqldatabaseimport), from Azure CLI using [az sql db export](/cli/azure/sql/db#az-sql-db-export) and [az sql db import](/cli/azure/sql/db#az-sql-db-import), and from [REST API](/rest/api/sql/) isn't supported. Bacpac import/export for smaller Hyperscale databases (up to 200 GB) is supported using SSMS and [SqlPackage](/sql/tools/sqlpackage) version 18.4 and later. For larger databases, bacpac export/import may take a long time, and may fail for various reasons. |
 | Elastic Pools |  Elastic Pools aren't currently supported with Hyperscale.|
 | Migration of databases with In-Memory OLTP objects | Hyperscale supports a subset of In-Memory OLTP objects, including memory-optimized table types, table variables, and natively compiled modules. However, when any In-Memory OLTP objects are present in the database being migrated, migration from Premium and Business Critical service tiers to Hyperscale isn't supported. To migrate such a database to Hyperscale, all In-Memory OLTP objects and their dependencies must be dropped. After the database is migrated, these objects can be recreated. Durable and non-durable memory-optimized tables aren't currently supported in Hyperscale, and must be changed to disk tables.|
-| Shrink Database | DBCC SHRINKDATABASE or DBCC SHRINKFILE isn't currently supported for Hyperscale databases. |
+| Shrink Database | DBCC SHRINKDATABASE, DBCC SHRINKFILE or setting AUTO_SHRINK to ON at the database level, are not currently supported for Hyperscale databases. |
 | Database integrity check | DBCC CHECKDB isn't currently supported for Hyperscale databases. DBCC CHECKTABLE ('TableName') WITH TABLOCK  and DBCC CHECKFILEGROUP WITH TABLOCK may be used as a workaround. See [Data Integrity in Azure SQL Database](https://azure.microsoft.com/blog/data-integrity-in-azure-sql-database/) for details on data integrity management in Azure SQL Database. |
 | Elastic Jobs | Using a Hyperscale database as the Job database isn't supported. However, elastic jobs can target Hyperscale databases in the same way as any other database in Azure SQL Database. |
 |Data Sync| Using a Hyperscale database as a Hub or Sync Metadata database isn't supported. However, a Hyperscale database can be a member database in a Data Sync topology. |

azure-sql/managed-instance/doc-changes-updates-known-issues.md

@@ -20,6 +20,7 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
 
 |Issue  |Date discovered  |Status  |Date resolved  |
 |---------|---------|---------|---------|
+|[Interim guidance on 2022 time zone updates for Chile](#interim-guidance-on-2022-time-zone-updates-for-chile)|Aug 2022|Has Workaround||
 |[Querying external table fails with 'not supported' error message](#querying-external-table-fails-with-not-supported-error-message)|Jan 2022|Has Workaround||
 |[When using SQL Server authentication, usernames with '@' are not supported](#when-using-sql-server-authentication-usernames-with--are-not-supported)|Oct 2021|Resolved|Feb 2022|
 |[Misleading error message on Azure portal suggesting recreation of the Service Principal](#misleading-error-message-on-azure-portal-suggesting-recreation-of-the-service-principal)|Sep 2021||Oct 2021|
@@ -58,6 +59,12 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
 
 ## Has workaround
 
+### Interim guidance on 2022 time zone updates for Chile
+
+On August 8, 2022, the Chilean government made an official announcement about a Daylight-Saving Time (DST) [time zone change](https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/interim-guidance-on-2022-time-zone-updates-for-chile/ba-p/3598290). Starting at 12:00 a.m. Saturday, September 10, 2022, until 12:00 a.m. Saturday, April 1, 2023, the official time will advance 60 minutes. The change affects the following three time zones:  **Pacific SA Standard Time**, **Easter Island Standard Time** and **Magallanes Standard Time**. Azure SQL Managed Instances using affected time zones will not reflect the changes [until Microsoft releases an OS update](https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/interim-guidance-on-2022-time-zone-updates-for-chile/ba-p/3598290) to support this and Azure SQL Managed Instance service absorbs the update on the OS level.
+
+**Workaround**: If you need to alter affected time zones for your managed instances, please be aware of the [limitations](timezones-overview.md#limitations) and follow the guidance from the documentation.
+
 ### Querying external table fails with not supported error message
 Querying external table may fail with generic error message "_Queries over external tables are not supported with the current service tier or performance level of this database. Consider upgrading the service tier or performance level of the database_". The only type of external table supported in Azure SQL Managed Instance are PolyBase external tables (in preview). To allow queries on PolyBase external tables, you need to enable PolyBase on managed instance by running sp_configure command. 
 

azure-sql/managed-instance/managed-instance-link-feature-overview.md

@@ -1,11 +1,11 @@
 ---
-title: The link feature
+title: Link feature for Azure SQL Managed Instance (preview)
 titleSuffix: Azure SQL Managed Instance
 description: Learn about the link feature for Azure SQL Managed Instance to continuously replicate data from SQL Server to the cloud, or migrate your SQL Server databases with the best possible minimum downtime.
 author: danimir
 ms.author: danil
-ms.reviewer: mathoma, danil
-ms.date: 08/30/2022
+ms.reviewer: mathoma, danil, randolphwest
+ms.date: 09/01/2022
 ms.service: sql-managed-instance
 ms.subservice: data-movement
 ms.topic: conceptual

azure-sql/managed-instance/timezones-overview.md

@@ -28,6 +28,9 @@ A set of supported time zones is inherited from the underlying operating system
 
 A list with names of the supported time zones is exposed through the [sys.time_zone_info](/sql/relational-databases/system-catalog-views/sys-time-zone-info-transact-sql) system view.
 
+> [!NOTE]
+> On August 8, 2022, the Chilean government made an official announcement about a Daylight-Saving Time (DST) [time zone change](https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/interim-guidance-on-2022-time-zone-updates-for-chile/ba-p/3598290). Starting at 12:00 a.m. Saturday, September 10, 2022, until 12:00 a.m. Saturday, April 1, 2023, the official time will advance 60 minutes. The change affects the following three time zones: **Pacific SA Standard Time**, **Easter Island Standard Time** and **Magallanes Standard Time**. Azure SQL Managed Instances using affected time zones will not reflect the changes [until Microsoft releases an OS update](https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/interim-guidance-on-2022-time-zone-updates-for-chile/ba-p/3598290) to support this and Azure SQL Managed Instance service absorbs the update on the OS level. If you need to alter affected time zones for your managed instances, please be aware of the [limitations](#limitations) and follow the guidance from the documentation.
+
 ## Set a time zone
 
 A time zone of a managed instance can be set during instance creation only. The default time zone is UTC.

azure-sql/virtual-machines/windows/availability-group-manually-configure-multiple-regions.md

@@ -3,8 +3,8 @@ title: Configure a SQL Server Always On availability group across different regi
 description: This article explains how to configure a SQL Server Always On availability group on Azure virtual machines with a replica in a different region.
 author: adbadram
 ms.author: adbadram
-ms.reviewer: mathoma
-ms.date: "05/02/2017"
+ms.reviewer: mathoma, randolphwest
+ms.date: 09/01/2022
 ms.service: virtual-machines-sql
 ms.subservice: hadr
 ms.topic: how-to
@@ -19,6 +19,9 @@ tags: azure-service-management
 
 This article explains how to configure a SQL Server Always On availability group replica on Azure virtual machines in a remote Azure location. Use this configuration to support disaster recovery.
 
+> [!NOTE]  
+> You can use the same steps in this article to extend your on-premises availability group to Azure.
+
 This article applies to Azure Virtual Machines in Resource Manager mode.
 
 The following image shows a common deployment of an availability group on Azure virtual machines:

docs/azure-data-studio/preview-features.md

@@ -43,46 +43,24 @@ You can enable or disable preview features anytime in your Settings.
 * Backup / Restore
 * Deployments
     * SQL Edge
-    * SQL Server Big Data Cluster
-    * SQL Server container image
-    * SQL Server on Windows
 * Feature tour
-* SQLCMD mode
-* New Welcome page
 
 ### Notebook features in preview
 
 * Dotnet interactive support
-* Markdown toolbar
-* New Notebook toolbar
-* Notebook kernels
-    * Kusto
-    * PowerShell
-    * PySpark
-    * Python
-    * Spark | Scala
-    * Spark | R
-    * SQL
-* Open Notebook from browser
-* Pinned Notebooks
-* Python dependencies wizard
 
 ### First-party extensions in preview
 
-* Admin Pack for SQL Server
 * Azure Monitor Logs
 * Azure SQL Edge Deployment
-* Azure Synapse Analytics Insights
 * Central Management Servers
 * Cosmos
 * Database Administration Tool Extensions for Windows
 * Database Migration Assessment for Oracle
 * Kusto
-* Machine Learning
 * Managed Instance Dashboard
 * Oracle
 * PostgreSQL
-* PowerShell
 * Query History
 * SandDance for Azure Data Studio
 * Server Reports

docs/big-data-cluster/cluster-manage-notebooks.md

@@ -8,8 +8,8 @@ ms.date: 6/21/2022
 ms.prod: sql
 ms.technology: big-data-cluster
 ms.topic: conceptual
-ms.metadata: seo-lt-2019
 ms.custom: kr2b-contr-experiment
+ms.metadata: seo-lt-2019
 ---
 
 # An Index of Management notebooks for SQL Server Big Data Clusters

docs/big-data-cluster/troubleshoot-ad-hung-deployment-unhealthy-sparkhead-pods.md

@@ -1,15 +1,15 @@
 ---
-title: 'AD mode deployment becomes unresponsive: sparkhead pods'
+title: "AD mode deployment becomes unresponsive: sparkhead pods"
 titleSuffix: SQL Server Big Data Cluster
 description: Troubleshooting unresponsive deployment of a SQL Server Big Data Cluster in an Active Directory domain with unhealthy sparkhead pods.
 author: macarv-ms
 ms.author: macarv
 ms.reviewer: wiassaf
 ms.date: 06/17/2022
-ms.custom: kr2b-contr-experiment
 ms.prod: sql
 ms.technology: big-data-cluster
 ms.topic: troubleshooting
+ms.custom: kr2b-contr-experiment
 ---
 
 # Active Directory mode deployment becomes unresponsive: sparkhead pods

docs/connect/ado-net/add-existing-constraints-to-dataset.md

@@ -1,16 +1,14 @@
 ---
 title: "Add existing constraints to a DataSet"
 description: Describes how to add existing constraints to a DataSet.
+author: David-Engel
+ms.author: v-davidengel
 ms.date: "11/30/2020"
-dev_langs: 
-  - "csharp"
-ms.assetid: 307d2809-208b-4cf8-b6a9-5d16f15fc16c
 ms.prod: sql
-ms.prod_service: connectivity
 ms.technology: connectivity
 ms.topic: conceptual
-author: David-Engel
-ms.author: v-davidengel
+dev_langs:
+  - "csharp"
 ---
 # Add existing constraints to a DataSet