Merge pull request #29963 from MicrosoftDocs/rw-0228-pre-ssms

Refresh in advance of SSMS release

Author: MikeRayMSFT

docs/relational-databases/errors-events/includes/sql-server-2016-database-engine-events-and-errors-10000-10999.md

@@ -33,7 +33,7 @@ ms.topic: include
 | 10042 | 16 | No | Cannot set any properties while there is an open rowset. |
 | 10052 | 16 | No | The insertion was canceled by the provider during notification. |
 | 10053 | 16 | No | Could not convert the data value due to reasons other than sign mismatch or overflow. |
-| 10054 | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
+| [10054](../mssqlserver-10054-database-engine-error.md) | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
 | 10055 | 16 | No | The data violated the integrity constraints for one or more columns. |
 | 10056 | 16 | No | The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. |
 | 10057 | 16 | No | Cannot create the row. Would exceed the total number of active rows supported by the rowset. |

docs/relational-databases/errors-events/includes/sql-server-2017-database-engine-events-and-errors-10000-10999.md

@@ -33,7 +33,7 @@ ms.topic: include
 | 10042 | 16 | No | Cannot set any properties while there is an open rowset. |
 | 10052 | 16 | No | The insertion was canceled by the provider during notification. |
 | 10053 | 16 | No | Could not convert the data value due to reasons other than sign mismatch or overflow. |
-| 10054 | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
+| [10054](../mssqlserver-10054-database-engine-error.md) | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
 | 10055 | 16 | No | The data violated the integrity constraints for one or more columns. |
 | 10056 | 16 | No | The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. |
 | 10057 | 16 | No | Cannot create the row. Would exceed the total number of active rows supported by the rowset. |

docs/relational-databases/errors-events/includes/sql-server-2019-database-engine-events-and-errors-10000-10999.md

@@ -33,7 +33,7 @@ ms.topic: include
 | 10042 | 16 | No | Cannot set any properties while there is an open rowset. |
 | 10052 | 16 | No | The insertion was canceled by the provider during notification. |
 | 10053 | 16 | No | Could not convert the data value due to reasons other than sign mismatch or overflow. |
-| 10054 | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
+| [10054](../mssqlserver-10054-database-engine-error.md) | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
 | 10055 | 16 | No | The data violated the integrity constraints for one or more columns. |
 | 10056 | 16 | No | The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. |
 | 10057 | 16 | No | Cannot create the row. Would exceed the total number of active rows supported by the rowset. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-10000-10999.md

@@ -33,7 +33,7 @@ ms.topic: include
 | 10042 | 16 | No | Cannot set any properties while there is an open rowset. |
 | 10052 | 16 | No | The insertion was canceled by the provider during notification. |
 | 10053 | 16 | No | Could not convert the data value due to reasons other than sign mismatch or overflow. |
-| 10054 | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
+| [10054](../mssqlserver-10054-database-engine-error.md) | 16 | No | The data value for one or more columns overflowed the type used by the provider. |
 | 10055 | 16 | No | The data violated the integrity constraints for one or more columns. |
 | 10056 | 16 | No | The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. |
 | 10057 | 16 | No | Cannot create the row. Would exceed the total number of active rows supported by the rowset. |

docs/relational-databases/errors-events/mssqlserver-10054-database-engine-error.md

@@ -0,0 +1,45 @@
+---
+title: MSSQLSERVER_10054
+description: "MSSQLSERVER_10054"
+author: erinstellato-ms
+ms.author: erinstellato
+ms.reviewer: maghan, randolphwest
+ms.date: 02/29/2024
+ms.service: sql
+ms.subservice: supportability
+ms.topic: "reference"
+helpviewer_keywords:
+  - "10054 (Database Engine error)"
+---
+# MSSQLSERVER_10054
+
+[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+
+## Details
+
+| Attribute | Value |
+| --- | --- |
+| Product Name | SQL Server |
+| Event ID | 10054 |
+| Event Source | MSSQLSERVER |
+| Component | SQLEngine |
+| Symbolic Name | |
+| Message Text | A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Framework Microsoft SqlClient Data Provider). |
+
+## Explanation
+
+A connection to the server was attempted and established, but then before signing in, an error occurred.
+
+This error can occur when trying to connect to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] using a lower level of encryption than required.
+
+## User action
+
+To find the cause of the error, review the configuration for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. For information on how to encrypt connections for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], see [Configure SQL Server Database Engine for encrypting connections](../../database-engine/configure-windows/configure-sql-server-encryption.md).
+
+For more information related to troubleshooting, see [An existing connection was forcibly closed by the remote host (OS error 10054)](/troubleshoot/sql/database-engine/connect/tls-exist-connection-closed).
+
+## Related content
+
+- [Special cases for encrypting connections to SQL Server](../../database-engine/configure-windows/special-cases-for-encrypting-connections-sql-server.md)
+- [Certificate requirements for SQL Server](../../database-engine/configure-windows/certificate-requirements.md)
+- [TDS 8.0](../security/networking/tds-8.md)

docs/relational-databases/security/networking/tds-8.md

@@ -4,29 +4,29 @@ description: This article discusses TDS 8.0, the application layer protocol used
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: randolphwest
-ms.date: 08/02/2023
+ms.date: 02/29/2024
 ms.service: sql
 ms.subservice: security
 ms.topic: conceptual
-monikerRange: ">= sql-server-ver16||>= sql-server-linux-ver16||=azuresqldb-current||=azuresqldb-mi-current"
+monikerRange: ">=sql-server-ver16 || >=sql-server-linux-ver16 || =azuresqldb-current || =azuresqldb-mi-current"
 ---
 # TDS 8.0
 
 [!INCLUDE [SQL Server 2022, Azure SQL Database, Azure SQL Managed Instance](../../../includes/applies-to-version/sqlserver2022-asdb-asmi.md)]
 
 [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)], [!INCLUDE [ssazure-sqldb](../../../includes/ssazure-sqldb.md)], and [!INCLUDE [ssazuremi-md](../../../includes/ssazuremi-md.md)] support Tabular Data Stream (TDS) 8.0.
 
-The [Tabular Data Stream (TDS)](/openspecs/windows_protocols/ms-tds/b46a581a-39de-4745-b076-ec4dbb7d13ec) protocol is an application layer protocol used by clients to connect to SQL Server, while SQL Server uses Transport Layer Security (TLS) to encrypt data that is transmitted across a network between an instance of SQL Server and a client application.
+The [Tabular Data Stream (TDS)](/openspecs/windows_protocols/ms-tds/b46a581a-39de-4745-b076-ec4dbb7d13ec) protocol is an application layer protocol used by clients to connect to SQL Server. SQL Server uses Transport Layer Security (TLS) to encrypt data that is transmitted across a network between an instance of SQL Server and a client application.
 
-TDS is a secure protocol, but in previous versions of SQL Server, encryption could be turned off or not enabled. To meet the standards of mandatory encryption while using SQL Server, an iteration of the TDS protocol was introduced: TDS 8.0
+TDS is a secure protocol, but in previous versions of SQL Server, encryption could be turned off or not enabled. To meet the standards of mandatory encryption while using SQL Server, an iteration of the TDS protocol was introduced: TDS 8.0.
 
-The TLS handshake now precedes any TDS messages, wrapping the TDS session in TLS to enforce encryption, making TDS 8.0 aligned with HTTPS and other web protocols. This significantly contributes to TDS traffic manageability as standard network appliances are now able to filter and securely passthrough SQL queries.
+The TLS handshake now precedes any TDS messages, wrapping the TDS session in TLS to enforce encryption, making TDS 8.0 aligned with HTTPS and other web protocols. This significantly contributes to TDS traffic manageability, as standard network appliances are now able to filter and securely passthrough SQL queries.
 
 Another benefit to TDS 8.0 compared to previous TDS versions is compatibility with TLS 1.3, and TLS standards to come. TDS 8.0 is also fully compatible with TLS 1.2 and previous TLS versions.
 
 ## How TDS works
 
-The Tabular Data Stream (TDS) protocol is an application-level protocol used for the transfer of requests and responses between clients and database server systems. In such systems, the client will typically establish a long-lived connection with the server. Once the connection is established using a transport-level protocol, TDS messages are used to communicate between the client and the server.
+The Tabular Data Stream (TDS) protocol is an application-level protocol used for the transfer of requests and responses between clients and database server systems. In such systems, the client typically establishes a long-lived connection with the server. Once the connection is established using a transport-level protocol, TDS messages are used to communicate between the client and the server.
 
 During the TDS session lifespan, there are three phases:
 
@@ -44,7 +44,7 @@ TCP handshake :arrow_right: TLS handshake :arrow_right: TDS prelogin (encrypted)
 
 ## Strict connection encryption
 
-To use TDS 8.0, [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] added `strict` as an additional connection encryption type to SQL Server drivers (`Encrypt=strict`). Download the latest version of the .NET, ODBC, OLE DB, JDBC, PHP and Python drivers to use the `strict` connection encryption type.
+To use TDS 8.0, [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] added `strict` as an additional connection encryption type to SQL Server drivers (`Encrypt=strict`). To use the `strict` connection encryption type, download the latest version of the .NET, ODBC, OLE DB, JDBC, PHP, and Python drivers.
 
 - [Microsoft ADO.NET for SQL Server and Azure SQL Database](../../../connect/ado-net/microsoft-ado-net-sql-server.md) version 5.1 or higher
 - [ODBC Driver for SQL Server](../../../connect/odbc/download-odbc-driver-for-sql-server.md) version 18.1.2.1 or higher
@@ -59,7 +59,7 @@ In order to prevent a man-in-the-middle attack with `strict` connection encrypti
 
 The `Force Strict Encryption` option added with TDS 8.0 in SQL Server Network Configuration forces all clients to use `strict` as the encryption type. Any clients or features without the `strict` connection encryption fail to connect to SQL Server.
 
-The following is a list of features or tools that still use previous version of drivers that don't support TDS 8.0, and as such, may not work with the `strict` connection encryption:
+The following features or tools still use previous version of drivers that don't support TDS 8.0, and as such, might not work with the `strict` connection encryption:
 
 - Always On availability groups
 - Always On failover cluster instance (FCI)
@@ -80,9 +80,9 @@ The following additions are added to connection strings for encryption:
 | Keyword | Default | Description |
 | --- | --- | --- |
 | **Encrypt** | *false* | **Existing behavior**<br />When `true`, SQL Server uses TLS encryption for all data sent between the client and server if the server has a certificate installed. Recognized values are `true`, `false`, `yes`, and `no`. For more information, see [Connection String Syntax](/dotnet/framework/data/adonet/connection-string-syntax).<br /><br />**Change of behavior**<br />When set to `strict`, SQL Server uses TDS 8.0 for all data sent between the client and server.<br /><br />When set to `mandatory`, `true`, or `yes`, SQL Server uses TDS 7.x with TLS/SSL encryption for all data sent between the client and server if the server has a certificate installed.<br /><br />When set to `optional`, `false`, or `no`, the connection uses TDS 7.x and would be encrypted only if required by the SQL Server. |
-| **TrustServerCertificate** | *false* | **Existing behavior**<br />Set to `true` to specify that the driver doesn't validate the server TLS/SSL certificate. If `true`, the server TLS/SSL certificate is automatically trusted when the communication layer is encrypted using TLS.<br /><br />If `false`, the driver validates the server TLS/SSL certificate. If the server certificate validation fails, the driver raises an error and closes the connection. The default value is `false`. Make sure the value passed to `serverName` exactly matches the `Common Name (CN)` or DNS name in the `Subject Alternate Name` in the server certificate for a TLS/SSL connection to succeed.<br /><br />**Change of behavior for Microsoft ODBC Driver 18 for SQL Server**<br />If **Encrypt** is set to `strict`, this setting specifies the location of the certificate to be used for server certificate validation (exact match). The driver supports PEM, DER, and CER file extensions.<br /><br />If Encrypt is set to `true` or `false`, and the `TrustServerCertificate` property is unspecified or set to `null`, `true` or `false`, the driver uses the `ServerName` property value on the connection URL as the host name to validate the SQL Server TLS/SSL certificate. |
+| **TrustServerCertificate** | *false* | **Existing behavior**<br />Set to `true` to specify that the driver doesn't validate the server TLS/SSL certificate. If `true`, the server TLS/SSL certificate is automatically trusted when the communication layer is encrypted using TLS.<br /><br />If `false`, the driver validates the server TLS/SSL certificate. If the server certificate validation fails, the driver raises an error and closes the connection. The default value is `false`. Make sure the value passed to `serverName` exactly matches the `Common Name (CN)` or DNS name in the `Subject Alternate Name` in the server certificate for a TLS/SSL connection to succeed.<br /><br />**Change of behavior for Microsoft ODBC Driver 18 for SQL Server**<br />If **Encrypt** is set to `strict`, this setting specifies the location of the certificate to be used for server certificate validation (exact match). The driver supports PEM, DER, and CER file extensions.<br /><br />If Encrypt is set to `true` or `false`, and the `TrustServerCertificate` property is unspecified or set to `null`, `true`, or `false`, the driver uses the `ServerName` property value on the connection URL as the host name to validate the SQL Server TLS/SSL certificate. |
 | **HostNameInCertificate** | *null* | The host name to be used in validating the SQL Server TLS/SSL certificate. If the **HostNameInCertificate** property is unspecified or set to `null`, the driver uses the `ServerName` property value as the host name to validate the SQL Server TLS/SSL certificate. |
 
-## Next steps
+## Related content
 
 - [Connect to SQL Server with strict encryption](connect-with-strict-encryption.md)