Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: fenxu

docs/analytics-platform-system/tsql-system-views.md

@@ -225,7 +225,7 @@ For more reference information, see [T-SQL language elements](tsql-language-elem
 <!--Image references-->
 
 <!--Article references-->
-[SQL Data Warehouse reference overview]: sql-data-warehouse-overview-reference.md
+[Azure Synapse Analytics reference overview]: sql-data-warehouse-overview-reference.md
 
 <!--MSDN references-->
 

docs/azure-data-studio/azure-resource-explorer.md

@@ -96,4 +96,4 @@ Azure Resource Explorer provide quick access that helps you connect to SQL Serve
 ## Next steps
 
 - [Use [!INCLUDE[Azure Data Studio](../includes/name-sos-short.md)] to connect and query Azure SQL database](quickstart-sql-database.md)
-- [Use [!INCLUDE[Azure Data Studio](../includes/name-sos-short.md)] to connect and query data in Azure SQL Data Warehouse](quickstart-sql-dw.md)
+- [Use [!INCLUDE[Azure Data Studio](../includes/name-sos-short.md)] to connect and query data in Azure Synapse Analytics](quickstart-sql-dw.md)

docs/azure-data-studio/download-azure-data-studio.md

@@ -173,7 +173,7 @@ In an offline environment updates can be applied by [installing the latest versi
 
 ## Supported SQL offerings
 
-- This version of Azure Data Studio works with all [supported versions of SQL Server 2014 - [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)]](https://support.microsoft.com/lifecycle?C2=1044) and provides support for working with the latest cloud features in Azure SQL Database and Azure SQL Data Warehouse. Azure Data Studio also provides preview support for Azure SQL Managed Instance.
+- This version of Azure Data Studio works with all [supported versions of SQL Server 2014 - [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)]](https://support.microsoft.com/lifecycle?C2=1044) and provides support for working with the latest cloud features in Azure SQL Database and Azure Synapse Analytics. Azure Data Studio also provides preview support for Azure SQL Managed Instance.
 
 ## Upgrade from SQL Operations Studio
 

docs/azure-data-studio/faq.md

@@ -176,9 +176,9 @@ SQL PowerShell is available today on the PowerShell gallery and you can use it o
 
 Developers and DBAs are usually the users of Azure Data Studio.
 
-## Does Azure Data Studio integrate with Azure SQL Data Warehouse?
+## Does Azure Data Studio integrate with Azure Synapse Analytics?
 
-Yes. Azure Data Studio support for Azure SQL Data Warehouse is currently in preview, together with Azure SQL Managed Instance, and SQL Server 2019 Big Data.
+Yes. Azure Data Studio support for Azure Synapse Analytics is currently in preview, together with Azure SQL Managed Instance, and SQL Server 2019 Big Data.
 
 ## Why is Azure Data Studio important for the new version of SQL Server?
 

docs/azure-data-studio/index.yml

@@ -35,7 +35,7 @@ landingContent:
             url: quickstart-sql-server.md
           - text: Connect and query Azure SQL database
             url: quickstart-sql-database.md
-          - text: Connect and query data in Azure SQL data warehouse
+          - text: Connect and query data in Azure Synapse Analytics
             url: quickstart-sql-dw.md
           - text: Connect and query data in  PostgreSQL
             url: quickstart-postgres.md

docs/connect/odbc/linux-mac/connecting-with-sqlcmd.md

@@ -216,7 +216,7 @@ See [DSN and Connection String Keywords and Attributes](../dsn-connection-string
 
 In a DSN, only the DRIVER entry is required, but to connect to a remote server, `sqlcmd` or `bcp` needs a value in the SERVER element. If the SERVER element is empty or not present in the DSN, `sqlcmd` and `bcp` will attempt to connect to the default instance on the local system.
 
-When using bcp on Windows systems, [!INCLUDE[sql-server-2017](../includes/sssqlv14-md.md)] and earlier require the SQL Native Client 11 driver (sqlncli11.dll) while [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] and higher require the Microsoft ODBC Driver 17 for SQL Server driver (msodbcsql17.dll).  
+When using bcp on Windows systems, [!INCLUDE [sssql17-md](../../../includes/sssql17-md.md)] and earlier require the SQL Native Client 11 driver (sqlncli11.dll) while [!INCLUDE [sssqlv15-md](../../../includes/sssqlv15-md.md)] and higher require the Microsoft ODBC Driver 17 for SQL Server driver (msodbcsql17.dll).  
 
 If the same option is specified in both the DSN and the `sqlcmd` or `bcp` command line, the command line option overrides the value used in the DSN. For example, if the DSN has a DATABASE entry and the `sqlcmd` command line includes **-d**, the value passed to **-d** is used. If **Trusted_Connection=yes** is specified in the DSN, Kerberos authentication is used and user name (**-U**) and password (**-P**), if provided, are ignored.
 

docs/database-engine/log-shipping/about-log-shipping-sql-server.md

@@ -29,7 +29,7 @@ monikerRange: ">=sql-server-2016||=sqlallproducts-allversions"
 ---
 # About Log Shipping (SQL Server)
 
-[!INCLUDE [SQL Server Windows Only - ASDBMI ](../../includes/applies-to-version/sql-windows-only-asdbmi.md)]
+[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
   [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Log shipping allows you to automatically send transaction log backups from a *primary database* on a *primary server* instance to one or more *secondary databases* on separate *secondary server* instances. The transaction log backups are applied to each of the secondary databases individually. An optional third server instance, known as the *monitor server*, records the history and status of backup and restore operations and, optionally, raises alerts if these operations fail to occur as scheduled.  
 

docs/machine-learning/connect/loopback-connection.md

@@ -4,7 +4,7 @@ description: Learn how to use a loopback connection to connect back to SQL Serve
 ms.prod: sql
 ms.technology: machine-learning-services
 ms.date: 08/20/2020
-ms.topic: conceptual
+ms.topic: how-to
 author: Aniruddh25
 ms.author: anmunde
 ms.reviewer: dphansen

docs/relational-databases/backup-restore/sql-server-backup-to-url.md

@@ -77,8 +77,6 @@ Backup of a large database to blob storage is subject to the limitations listed
 
 ##  <a name="limitations"></a> Limitations  
 
--   Backup to premium storage is not supported.  
-  
 -   SQL Server limits the maximum backup size supported using a page blob to 1 TB. The maximum backup size supported using block blobs is limited to approximately 200 GB (50,000 blocks * 4MB MAXTRANSFERSIZE). Block blobs support striping to support substantially larger backup sizes.  
 
     > [!IMPORTANT]  
@@ -103,6 +101,8 @@ Backup of a large database to blob storage is subject to the limitations listed
 - If your server accesses Azure via a proxy server, you must use trace flag 1819 and then set the WinHTTP proxy configuration via one of the following methods:
    - The [proxycfg.exe](/windows/win32/winhttp/proxycfg-exe--a-proxy-configuration-tool) utility on Windows XP or Windows Server 2003 and earlier. 
    - The [netsh.exe](/windows/win32/winsock/netsh-exe) utility on Windows Vista and Windows Server 2008 or later. 
+
+- [Immutable storage for Azure Blob storage](/azure/storage/blobs/storage-blob-immutable-storage) is not supported. Set the **Immutable Storage** policy to false. 
 
 ## Supported arguments & statements
 

docs/relational-databases/databases/sql-server-data-files-in-microsoft-azure.md

@@ -171,25 +171,30 @@ For more information, see [Manage Access to Azure Storage Resources](https://doc
 
  **Database errors**  
 
-1.  *Errors when creating a database*   
-    Resolution: Review the instructions given in Lesson 4 in [Tutorial: Using the Microsoft Azure Blob storage service with SQL Server 2016 databases](../lesson-4-restore-database-to-virtual-machine-from-url.md).  
+**Errors when creating a database**
+Resolution: Review the instructions given in Lesson 4 in [Tutorial: Using the Microsoft Azure Blob storage service with SQL Server 2016 databases](../lesson-4-restore-database-to-virtual-machine-from-url.md).  
 
-2.  *Errors when running the Alter statement*   
-    Resolution: Make sure to execute the Alter Database statement when the database is online. When copying the data files to Azure Storage, always create a page blob not a block blob. Otherwise, ALTER Database will fail. Review the instructions given in Lesson 7 in [Tutorial: Using the Microsoft Azure Blob storage service with SQL Server 2016 databases](../tutorial-use-azure-blob-storage-service-with-sql-server-2016.md).  
+**Errors when running the Alter statement** 
+Resolution: Make sure to execute the Alter Database statement when the database is online. When copying the data files to Azure Storage, always create a page blob not a block blob. Otherwise, ALTER Database will fail. Review the instructions given in Lesson 7 in [Tutorial: Using the Microsoft Azure Blob storage service with SQL Server 2016 databases](../tutorial-use-azure-blob-storage-service-with-sql-server-2016.md).  
 
-3.  *Error code 5120 Unable to open the physical file "%.\*ls". Operating system error %d: "%ls"*   
+**Error code - 5120 Unable to open the physical file "%.\*ls". Operating system error %d: "%ls"**   
 
-    Resolution: Currently, this new enhancement does not support more than one SQL Server instance accessing the same database files in Azure Storage at the same time. If ServerA is online with an active database file and if ServerB is accidentally started, and it also has a database which points to the same data file, the second server will fail to start the database with an error *code 5120 Unable to open the physical file "%.\*ls". Operating system error %d: "%ls"*.  
+Resolution: Currently, this new enhancement does not support more than one SQL Server instance accessing the same database files in Azure Storage at the same time. If ServerA is online with an active database file and if ServerB is accidentally started, and it also has a database which points to the same data file, the second server will fail to start the database with an error *code 5120 Unable to open the physical file "%.\*ls". Operating system error %d: "%ls"*.  
 
-     To resolve this issue, first determine if you need ServerA to access the database file in Azure Storage or not. If not, remove any connection between ServerA and the database files in Azure Storage. To do this, follow these steps:  
-  
-    1.  Set the file path of Server A to a local folder by using the ALTER Database statement.  
-  
-    2.  Set the database offline in Server A.  
-  
-    3.  Then, copy database files from Azure Storage to the local folder in Server A. This ensures that ServerA still has a copy of the database locally.  
-  
-    4.  Set the database online.  
+To resolve this issue, first determine if you need ServerA to access the database file in Azure Storage or not. If not, remove any connection between ServerA and the database files in Azure Storage. To do this, follow these steps:  
+
+1.  Set the file path of Server A to a local folder by using the ALTER Database statement.  
+
+2.  Set the database offline in Server A.  
+
+3.  Then, copy database files from Azure Storage to the local folder in Server A. This ensures that ServerA still has a copy of the database locally.  
+
+4.  Set the database online.
+
+**Error code 833 - I/O requests taking longer than 15 seconds to complete** 
+   
+   This error indicates the storage system is unable to meet the demands of the SQL Server workload. Either decrease IO activity from the application layer, or increase throughput capability on the storage layer. To learn more, see [Error 833](../errors-events/mssqlserver-833-database-engine-error.md). If performance problems persist, consider moving files to a different storage tier such as Premium or UltraSSD. For SQL Server on Azure VMs, see [optimizing storage performance](/azure/virtual-machines/premium-storage-performance).
+
 
 ## Next steps