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

Author: Learn Build Service GitHub App

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

@@ -84,6 +84,7 @@ These are the current limitations to the Elastic Jobs service.  We're actively w
 | Excessive Audit logs from Jobs database | The Elastic Job agent operates by constantly polling the Job database to check for the arrival of new jobs and other CRUD operations. If auditing is enabled on the server that houses a Jobs database, a large amount of audit logs may be generated by the Jobs database. This can be mitigated by filtering out these audit logs using the `Set-AzSqlServerAudit` command with a predicate expression.<BR/><BR/>For example:<BR/> `Set-AzSqlServerAudit -ResourceGroupName "ResourceGroup01" -ServerName "Server01" -BlobStorageTargetState Enabled -StorageAccountResourceId "/subscriptions/7fe3301d-31d3-4668-af5e-211a890ba6e3/resourceGroups/resourcegroup01/providers/Microsoft.Storage/storageAccounts/mystorage" -PredicateExpression "database_principal_name <> '##MS_JobAccount##'"`<BR/><BR/>This command will only filter out Job Agent to Jobs database audit logs, not Job Agent to any target databases audit logs.|
 | Private endpoints are not supported | Elastic Job Agents currently cannot connect to Databases and Elastic Pools which restrict connections to private endpoints.|
 | Use of a Hyperscale database as *Job database* | Using a Hyperscale database as a *Job database* isn't supported. However, elastic jobs can target Hyperscale databases in the same way as any other database in Azure SQL Database.|
+| Serverless DBs and auto-pausing with Elastic Jobs. | When the job database is a serverless database, databases targeted by elastic jobs support auto-pausing, but will be resumed by job connections. 
 
 ## Best practices for creating jobs
 

azure-sql/database/job-automation-overview.md

@@ -46,7 +46,7 @@ Consider the following job scheduling technologies on different platforms:
 - **Elastic Jobs** are Job Scheduling services that execute custom jobs on one or many databases in Azure SQL Database.
 - **SQL Agent Jobs** are executed by the SQL Agent service that continues to be used for task automation in SQL Server and is also included with Azure SQL Managed Instances. SQL Agent Jobs are not available in Azure SQL Database.
 
-Elastic Jobs can target [Azure SQL Databases](sql-database-paas-overview.md), [Azure SQL Database elastic pools](elastic-pool-overview.md), and Azure SQL Databases in [shard maps](elastic-scale-shard-map-management.md).
+Elastic Jobs can target [Azure SQL Databases](sql-database-paas-overview.md), [Azure SQL Database elastic pools](elastic-pool-overview.md).
 
 - For T-SQL script job automation in SQL Server and Azure SQL Managed Instance, consider [SQL Agent](../managed-instance/job-automation-managed-instance.md). 
 
@@ -56,7 +56,7 @@ It is worth noting differences between SQL Agent (available in SQL Server and as
 
 | |Elastic Jobs |SQL Agent |
 |---------|---------|---------|
-|**Scope** | Any number of databases in Azure SQL Database and/or data warehouses in the same Azure cloud as the job agent. Targets can be in different servers, subscriptions, and/or regions. <br><br>Target groups can be composed of individual databases or data warehouses, or all databases in a server, pool, or shard map (dynamically enumerated at job runtime). | Any individual database in the same instance as the SQL agent. The Multi Server Administration feature of SQL Server Agent allows for master/target instances to coordinate job execution, though this feature is not available in SQL managed instance. |
+|**Scope** | Any number of databases in Azure SQL Database and/or data warehouses in the same Azure cloud as the job agent. Targets can be in different servers, subscriptions, and/or regions (dynamically enumerated at job runtime). | Any individual database in the same instance as the SQL agent. The Multi Server Administration feature of SQL Server Agent allows for master/target instances to coordinate job execution, though this feature is not available in SQL managed instance. |
 |**Supported APIs and Tools** | Portal, PowerShell, T-SQL, Azure Resource Manager | T-SQL, SQL Server Management Studio (SSMS) |
 
 ## Elastic job targets

azure-sql/database/outbound-firewall-rule-overview.md

@@ -22,6 +22,7 @@ Outbound firewall rules limit network traffic from the Azure SQL [logical server
 - [OPENROWSET](/sql/t-sql/functions/openrowset-transact-sql)
 - [Bulk Insert](/sql/t-sql/statements/bulk-insert-transact-sql)
 - [Elastic query](elastic-query-overview.md)
+- [sp_invoke_external_rest_endpoint](https://learn.microsoft.com/sql/relational-databases/system-stored-procedures/sp-invoke-external-rest-endpoint-transact-sql)
 
 > [!IMPORTANT]
 > - This article applies to both Azure SQL Database and [dedicated SQL pool (formerly SQL DW)](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is) in Azure Synapse Analytics. These settings apply to all SQL Database and dedicated SQL pool (formerly SQL DW) databases associated with the server. For simplicity, the term 'database' refers to both databases in Azure SQL Database and Azure Synapse Analytics. Likewise, any references to 'server' is referring to the [logical SQL server](logical-servers.md) that hosts Azure SQL Database and dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics. This article does *not* apply to Azure SQL Managed Instance or dedicated SQL pools in Azure Synapse Analytics workspaces.

docs/connect/ado-net/download-microsoft-sqlclient-data-provider.md

@@ -3,7 +3,7 @@ title: Download Microsoft SqlClient Data Provider for SQL Server
 description: Download page for ADO.NET and Microsoft SqlClient Data Provider for SQL Server.
 author: David-Engel
 ms.author: v-davidengel
-ms.date: 07/26/2022
+ms.date: 01/11/2023
 ms.service: sql
 ms.subservice: connectivity
 ms.topic: conceptual
@@ -20,6 +20,7 @@ If you need to download the Microsoft.Data.SqlClient package for offline use, it
 
 ## Download stable versions of Microsoft SqlClient Data Provider for SQL Server
 
+* [5.1.0](https://www.nuget.org/packages/Microsoft.Data.SqlClient/5.1.0)
 * [5.0.0](https://www.nuget.org/packages/Microsoft.Data.SqlClient/5.0.0)
 * [4.1.0](https://www.nuget.org/packages/Microsoft.Data.SqlClient/4.1.0)
 * [4.0.1](https://www.nuget.org/packages/Microsoft.Data.SqlClient/4.0.1)

docs/connect/ado-net/introduction-microsoft-data-sqlclient-namespace.md

@@ -3,7 +3,7 @@ title: Introduction to Microsoft.Data.SqlClient namespace
 description: Learn about the Microsoft.Data.SqlClient namespace and how it's the preferred way to connect to SQL for .NET applications.
 author: David-Engel
 ms.author: v-davidengel
-ms.date: 07/26/2022
+ms.date: 01/11/2022
 ms.service: sql
 ms.subservice: connectivity
 ms.topic: conceptual
@@ -14,12 +14,39 @@ ms.topic: conceptual
 
 The Microsoft.Data.SqlClient namespace is essentially a new version of the System.Data.SqlClient namespace. Microsoft.Data.SqlClient generally maintains the same API and backwards compatibility with System.Data.SqlClient. To migrate from System.Data.SqlClient to Microsoft.Data.SqlClient, for most applications, it's simple. Add a NuGet dependency on Microsoft.Data.SqlClient and update references and `using` statements to Microsoft.Data.SqlClient.
 
-There are a few differences in less-used APIs compared to System.Data.SqlClient that may affect some applications. For those differences, see this useful [porting cheat sheet](https://github.com/dotnet/SqlClient/blob/main/porting-cheat-sheet.md).
+There are a few differences in less-used APIs compared to System.Data.SqlClient that may affect some applications. For those differences, refer to the useful [porting cheat sheet](https://github.com/dotnet/SqlClient/blob/main/porting-cheat-sheet.md).
 
 ## API reference
 
 The Microsoft.Data.SqlClient API details can be found in the [.NET API Browser](/dotnet/api/microsoft.data.sqlclient).
 
+### Breaking changes in 5.1
+
+- Dropped support for .NET Core 3.1. [#1704](https://github.com/dotnet/SqlClient/pull/1704) [#1823](https://github.com/dotnet/SqlClient/pull/1823)
+
+### New features in 5.1
+
+- Added support for `DateOnly` and `TimeOnly` for `SqlParameter` value and `GetFieldValue`. [#1813](https://github.com/dotnet/SqlClient/pull/1813)
+- Added support for TLS 1.3 for .NET Core and SNI Native. [#1821](https://github.com/dotnet/SqlClient/pull/1821)
+- Added `ServerCertificate` setting for `Encrypt=Mandatory` or `Encrypt=Strict`. [#1822](https://github.com/dotnet/SqlClient/pull/1822) [Read more](#server-certificate)
+- Added Windows ARM64 support when targeting .NET Framework. [#1828](https://github.com/dotnet/SqlClient/pull/1828)
+
+### Server Certificate
+
+The default value of the `ServerCertificate` connection setting is an empty string.  When `Encrypt` is set to `Mandatory` or `Strict`, `ServerCertificate` can be used to specify a path on the file system to a certificate file to match against the server's TLS/SSL certificate. The certificate specified must be an exact match to be valid. The accepted certificate formats are `PEM`, `DER`, and `CER`. Here's a usage example:
+
+ ```cs
+ "Data Source=...;Encrypt=Strict;ServerCertificate=C:\\certificates\\server.cer"
+ ```
+
+## 5.1 Target platform support
+
+- .NET Framework 4.6.2+ (Windows x86, Windows x64)
+- .NET 6.0+ (Windows x86, Windows x64, Windows ARM64, Windows Azure Resource Manager, Linux, macOS)
+- .NET Standard 2.0+ (Windows x86, Windows x64, Windows ARM64, Windows ARM, Linux, macOS)
+
+Full release notes, including dependencies, are available in the GitHub Repository: [5.1 Release Notes](https://github.com/dotnet/SqlClient/tree/main/release-notes/5.1).
+
 ## Release notes for Microsoft.Data.SqlClient 5.0
 
 ### Breaking changes in 5.0

docs/connect/ado-net/sqlclient-driver-support-lifecycle.md

@@ -3,7 +3,7 @@ title: SqlClient driver support lifecycle
 description: Product support lifecycle information for the Microsoft.Data.SqlClient .NET library.
 author: David-Engel
 ms.author: v-davidengel
-ms.date: 01/10/2023
+ms.date: 01/11/2023
 ms.service: sql
 ms.subservice: connectivity
 ms.topic: conceptual
@@ -27,7 +27,8 @@ New stable (GA) releases are published every six months on a regular cadence beg
 
 | Version | Official Release Date | Latest Patch Version | Patch Release Date | Support Level | End of Support |
 |--|--|--|--|--|--|
-| 5.0 | July 29, 2022 | 5.0.1 | October 11, 2022 | Current | - |
+| 5.1 | January 19, 2023 | - | - | LTS | January 20, 2026 |
+| 5.0 | July 29, 2022 | 5.0.1 | October 11, 2022 | Current | July 19, 2023 |
 | 4.1 | January 31, 2022 | 4.1.1 | September 13, 2022 | Current | January 29, 2023 |
 | 4.0 | November 18, 2021 | 4.0.2 | September 13, 2022 | LTS | November 19, 2024 |
 | 3.1 | March 30, 2022 | 3.1.1 | August 12, 2022 | LTS | March 30, 2025 |
@@ -64,16 +65,18 @@ Current releases are supported for three months after a subsequent Current or LT
 
 ## SQL version compatibility with Microsoft.Data.SqlClient
 
-|Database version&nbsp;&#8594;<br />&#8595; Driver Version|Azure SQL Database|Azure Synapse Analytics|Azure SQL Managed Instance|SQL Server 2019|SQL Server 2017|SQL Server 2016|SQL Server 2014|SQL Server 2012|
-|---|---|---|---|---|---|---|---|---|
-|5.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
-|4.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
-|4.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
-|3.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
-|2.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
-|2.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
-|1.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
-|1.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|Database version&nbsp;&#8594;<br />&#8595; Driver Version|Azure SQL Database|Azure Synapse Analytics|Azure SQL Managed Instance|SQL Server 2022|SQL Server 2019|SQL Server 2017|SQL Server 2016|SQL Server 2014|SQL Server 2012|
+|---|---|---|---|---|---|---|---|---|---|
+|5.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|5.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|4.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|4.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|3.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|3.0|No|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|2.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|2.0|No|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|1.1|No|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
+|1.0|No|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
 
 ## Supported OS versions
 
@@ -85,7 +88,7 @@ Microsoft.Data.SqlClient supports all operating systems supported by .NET Framew
 
 ### Support for .NET Core applications
 
-Microsoft.Data.SqlClient supports all operating systems supported by .NET Core v3.1 and above.
+Microsoft.Data.SqlClient supports all operating systems supported by .NET 6 and above.
 
 [.NET Core supported OS lifecycle policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md).
 

docs/linux/quickstart-install-connect-suse.md

@@ -4,7 +4,7 @@ description: This quickstart shows how to install SQL Server on SUSE Linux Enter
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: randolphwest
-ms.date: 12/21/2022
+ms.date: 01/18/2023
 ms.service: sql
 ms.subservice: linux
 ms.topic: conceptual
@@ -102,7 +102,9 @@ To configure [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] on SLES,
    sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
    ```
 
-1. Run the following commands to install [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]:
+1. Before you install [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], and after you have registered and activated your SUSE Linux Enterprise Server with SUSE Customer Center, you must activate both the [Desktop Applications module and Development Tools module](https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-register-sle.html). These modules are required for some of the [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] package dependencies.
+
+1. Now, you are ready to install [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. Run the following commands to install [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]:
 
    ```bash
    sudo zypper install -y mssql-server

docs/sql-server/azure-arc/assess.md

@@ -29,8 +29,9 @@ The Environment Health assessment is replaced with a much richer best practices
   > [!NOTE]
   > Best practices assessment is currently limited to SQL Server running on Windows machines. This will not work for SQL on Linux machines.
 
-- [A Log Analytics workspace](/azure/azure-monitor/logs/quick-create-workspace?tabs=azure-portal) in the same subscription as your Arc-enabled SQL Server resource to upload assessment results to.
+- Make sure that the version of Azure Extension for SQL Server (`WindowsAgent.SqlServerI`) is "**1.1.2202.47**" or above. Learn how to [check the **Azure Extension for SQL Server** version and update to the latest.](/azure/azure-arc/servers/manage-vm-extensions-portal#upgrade-extensions)
 
+- [A Log Analytics workspace](/azure/azure-monitor/logs/quick-create-workspace?tabs=azure-portal) in the same subscription as your Arc-enabled SQL Server resource to upload assessment results to.
 - The user configuring SQL BPA must have following permissions.
 
   - Log Analytics Contributor role on Resource Group or Subscription of the Log Analytics workspace.
@@ -52,8 +53,7 @@ Resource group or Subscription of Arc Machine.
 
 - The [SQL Server browser service](../../tools/configuration-manager/sql-server-browser-service.md) must be running if you're operating a named instance of SQL Server.
 
-- Upgrade the Azure SQL Server extension version. Use the latest version from the [release notes](/sql/sql-server/azure-arc/release-notes). You can upgrade to latest version by updating the extension, in the extension management of Arc-Server. For details, see [Upgrade extensions](/en-us/azure/azure-arc/servers/manage-vm-extensions-portal#upgrade-extensions).
-   
+  
 ## Enable best practices assessment
 
 1. Sign into the [Azure portal](https://portal.azure.com/) and go to your [Arc-enabled SQL Server resource](https://portal.azure.com/#view/Microsoft_Azure_HybridCompute/AzureArcCenterBlade/~/sqlServers)