Skip to content

Commit 80375fe

Browse files
Merge pull request #35903 from VanMSFT/vanmsft/work-2025-11-21
Database Mail | Update TDS 8.0 support documentation
2 parents 0fe6ef4 + 1e79ba9 commit 80375fe

2 files changed

Lines changed: 11 additions & 12 deletions

File tree

docs/relational-databases/database-mail/database-mail.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,10 @@ title: "Database Mail"
33
description: "Database Mail"
44
author: WilliamDAssafMSFT
55
ms.author: wiassaf
6-
ms.date: 05/16/2025
6+
ms.date: 11/21/2025
77
ms.service: sql
88
ms.topic: conceptual
9+
ai-usage: ai-assisted
910
helpviewer_keywords:
1011
- "architecture [SQL Server], Database Mail"
1112
- "Database Mail [SQL Server], architecture"
@@ -57,13 +58,13 @@ monikerRange: ">=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-cu
5758

5859
- Attachment size governor: Database Mail enforces a configurable limit on the attachment file size. You can change this limit by using the [sysmail_configure_sp](../system-stored-procedures/sysmail-configure-sp-transact-sql.md) stored procedure.
5960

60-
- Prohibited file extensions: Database Mail maintains a list of prohibited file extensions. Users cannot attach files with an extension that appears in the list. You can change this list by using sysmail_configure_sp.
61+
- Prohibited file extensions: Database Mail maintains a list of prohibited file extensions. Users can't attach files with an extension that appears in the list. You can change this list by using sysmail_configure_sp.
6162

6263
- Database Mail runs under the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Engine service account. To attach a file from a folder to an email, the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] engine account should have permissions to access the folder with the file.
6364

6465
### Supportability
6566

66-
- Integrated configuration: Database Mail maintains the information for e-mail accounts within [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)]. There is no need to manage a mail profile in an external client application. Database Mail Configuration Wizard provides a convenient interface for configuring Database Mail. You can also create and maintain Database Mail configurations using [!INCLUDE[tsql](../../includes/tsql-md.md)].
67+
- Integrated configuration: Database Mail maintains the information for e-mail accounts within [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)]. There's no need to manage a mail profile in an external client application. Database Mail Configuration Wizard provides a convenient interface for configuring Database Mail. You can also create and maintain Database Mail configurations using [!INCLUDE[tsql](../../includes/tsql-md.md)].
6768

6869
- Logging. Database Mail logs e-mail activity to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], the Microsoft Windows Application event log, and to tables in the `msdb` database.
6970

@@ -114,6 +115,10 @@ monikerRange: ">=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-cu
114115

115116
- A scheduled task, such as a database backup or replication event, succeeds or fails. For example, you can use [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent Mail to notify operators if an error occurs during processing at the end of a month.
116117

118+
## TDS 8.0 support
119+
120+
[!INCLUDE [sssql25-md](../../includes/sssql25-md.md)] introduces [TDS 8.0](../security/networking/tds-8.md) support for Database Mail. The TDS 8.0 protocol provides enhanced security and encryption for data transmitted between SQL Server and client applications. This allows Database Mail to work in environments where TLS 1.3 encryption and TDS 8.0 are enforced.
121+
117122
<a id="RelatedContent"></a>
118123

119124
## Related content

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

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,13 @@ description: This article discusses TDS 8.0, the application layer protocol used
44
author: VanMSFT
55
ms.author: vanto
66
ms.reviewer: randolphwest, jaferebe, jopilov
7-
ms.date: 09/04/2025
7+
ms.date: 11/21/2025
88
ms.service: sql
99
ms.subservice: security
1010
ms.topic: conceptual
1111
ms.custom:
1212
- ignite-2025
13+
ai-usage: ai-assisted
1314
monikerRange: ">=sql-server-ver16 || >=sql-server-linux-ver16 || =azuresqldb-current || =azuresqldb-mi-current || =fabric-sqldb"
1415
---
1516

@@ -80,6 +81,7 @@ For more information on how clients use different TDS versions, see the keywords
8081
- [bcp utility](../../../tools/bcp-utility.md#tds-80-support)
8182
- [SQL VSS Writer](../../../database-engine/configure-windows/sql-writer-service.md)
8283
- [SQL CEIP service](../../../sql-server/usage-and-diagnostic-data-configuration-for-sql-server.md)
84+
- [Database Mail](../../database-mail/database-mail.md)
8385
- [Polybase](../../polybase/polybase-guide.md#sql-server-2025-polybase-enhancements)
8486
- [Always On availability groups](connect-with-strict-encryption.md#connect-to-an-always-on-availability-group)
8587
- [Always On failover cluster instance (FCI)](connect-with-strict-encryption.md#connect-to-a-failover-cluster-instance)
@@ -104,14 +106,6 @@ To use TDS 8.0, [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] added `
104106

105107
In order to prevent a man-in-the-middle attack with `strict` connection encryption, users can't set the `TrustServerCertificate` option to `true` and allow any certificate the server provided. Instead, users would use the `HostNameInCertificate` option to specify the certificate `ServerName` that should be trusted. The certificate supplied by the server would need to pass the certificate validation. For more information on certificate validation, see [Certificate requirements for SQL Server](../../../database-engine/configure-windows/certificate-requirements.md)
106108

107-
### Features that don't support forcing strict encryption
108-
109-
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.
110-
111-
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:
112-
113-
- Database mail
114-
115109
## Additional changes to connection string encryption properties
116110

117111
The following options are added to connection strings to encrypt communication:

0 commit comments

Comments
 (0)