Skip to content

Commit 20d06a7

Browse files
haywoodsloanhaywoodsloan
committed
fill in draft
1 parent 366caee commit 20d06a7

1 file changed

Lines changed: 234 additions & 0 deletions

File tree

‎support/sql/releases/sqlserver-2025/cumulativeupdate1.md‎

Lines changed: 234 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,234 @@
1+
---
2+
title: Cumulative update 1 for SQL Server 2025 (KB5074901)
3+
description: This article contains the summary, known issues, improvements, fixes, and other information for SQL Server 2025 cumulative update 1 (KB5074901).
4+
ms.date: 01/15/2026
5+
ms.update-cycle: 1095-days
6+
ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, KB5074901
7+
ms.reviewer: v-shaywood
8+
appliesto:
9+
- SQL Server 2025 on Windows
10+
- SQL Server 2025 on Linux
11+
---
12+
13+
# KB5074901 - Cumulative Update 1 for SQL Server 2025
14+
15+
_Release Date:_   January 15, 2026
16+
_Version:_   17.0.4005.? TODO
17+
18+
## Summary
19+
20+
This article describes Cumulative Update package 1 (CU1) for Microsoft SQL Server 2025. This update contains 16 [fixes](#improvements-and-fixes-included-in-this-update) that were issued after the initial release of SQL Server 2025. It updates components in the following builds:
21+
22+
- SQL Server - Product version: **17.0.4005.?** TODO, file version: **?** TODO
23+
- Analysis Services - Product version: **?** TODO, file version: **?** TODO
24+
25+
## Known issues in this update
26+
27+
### Incorrect behavior of SESSION_CONTEXT in parallel plans
28+
29+
[!INCLUDE [av-session-context](../includes/av-sesssion-context.md)]
30+
31+
## Improvements and fixes included in this update
32+
33+
A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2025, SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Download this Excel file now](https://aka.ms/sqlserverbuilds).
34+
35+
> [!NOTE]
36+
> Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.
37+
38+
For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.
39+
40+
| Bug Reference | Description | Fix Area | Component | Platform |
41+
| :------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------- | :-------------------------------------- | :------- |
42+
| <a id=4729051>[4729051](#4729051)</a> | Fixes an issue where DBCC CHECKDB with EXTENDED_LOGICAL_CHECKS fails with an exception when there are both persisted and non-persisted computed columns in a table while trace flag 176 is enabled. | SQL Server Engine | Programmability | All |
43+
| <a id=4787271>[4787271](#4787271)</a> | Fixes an issue that was causing SQLCMD to crash when using the -N in a :CONNECT command. | SQL Connectivity | SQL Connectivity | Windows |
44+
| <a id=4796293>[4796293](#4796293)</a> | Fix incorrect CPU utilization metrics in sys.dm_os_ring_buffers DMV for SQL Server on Linux. | SQL Server Engine | Linux | Linux |
45+
| <a id=4796318>[4796318](#4796318)</a> | Fixed an issue causing SQL Server on Linux to crash when reading an invalid ID type from Domain Controller. | SQL Server Engine | Linux | Linux |
46+
| <a id=4796384>[4796384](#4796384)</a> | Fixed an issue in SQL Server on Linux preventing Active Directory logins to work when the keytab is updated after the privileged user password is rotated. | SQL Server Engine | Linux | Linux |
47+
| <a id=4809134>[4809134](#4809134)</a> | Fixes an issue that was causing SQL Server Configuration Manager (SSCM) to crash when importing a certificate. | SQL Server Client Tools | SQL Server Configuration Manager | Windows |
48+
| <a id=4814064>[4814064](#4814064)</a> | Fix an issue during a Daylight Savings Time "Fall Back" where timestamps may have an incorrect time zone. | SQL Server Engine | LibOS | Linux |
49+
| <a id=4814070>[4814070](#4814070)</a> | SQL Server 2025 can now be registered on Linux containers by setting the MSSQL_PID environment variable to StandardDeveloper or EnterpriseDeveloper. | SQL Setup | Linux | Linux |
50+
| <a id=4818774>[4818774](#4818774)</a> | Fixed an issue where VDI restore operations on Linux containers can run out of memory unexpectedly if memory is limited with a Linux cgroup. | SQL Server Engine | Linux | Linux |
51+
| <a id=4836615>[4836615](#4836615)</a> | Restricting privilege for dbcc stackdump so that only sysadmin can invoke the dump | SQL Server Engine | Security Infrastructure | All |
52+
| <a id=4860665>[4860665](#4860665)</a> | Enabling create and restore Database on Contained Availability Group Connection (Listener) to let Contained AG user to create and restore database without connection to SQL Instance. | SQL Server Engine | High Availability and Disaster Recovery | All |
53+
| <a id=4861315>[4861315](#4861315)</a> | If traceflag 15918 is enabled using DBCC TRACEON on a SQL Server instance with startup traceflag 15923 enabled, then it may cause the SQL Server process to crash. | SQL Server Engine | Resource Governor | All |
54+
| <a id=4861456>[4861456](#4861456)</a> | Adds an information message in the error log if the deprecated lightweight pooling configuration is enabled. | SQL Server Engine | SQL OS | Windows |
55+
| <a id=4866542>[4866542](#4866542)</a> | Removes `.rtf` from full-text system DMVs on Linux platform. This document type was previously incorrectly reported as supported. | SQL Server Engine | Search | Linux |
56+
| <a id=4866716>[4866716](#4866716)</a> | Allows the use of sys.fn_xe_file_target_read_file() function to read the system_health event session data in Azure SQL Managed Instance. | SQL Server Engine | SQL OS | Windows |
57+
| <a id=4873449>[4873449](#4873449)</a> | Fixes an issue where creating a full‑text index on a .docx file produced incorrect results when a paragraph began with a hyperlink and the preceding paragraph did not contain trailing whitespace. | SQL Server Engine | Search | All |
58+
59+
## How to obtain or download this or the latest cumulative update package
60+
61+
<details>
62+
<summary><b>How to obtain or download the latest cumulative update package for Windows (recommended)</b></summary>
63+
64+
The following update is available from the Microsoft Download Center:
65+
66+
:::image type="icon" source="../media/download-icon.png" border="false"::: [Download the latest cumulative update package for SQL Server 2025 now](https://www.microsoft.com/download/details.aspx?id=TODO)
67+
68+
> [!NOTE]
69+
>
70+
> - Microsoft Download Center always offers the latest SQL Server 2025 CU release.
71+
> - If the download page doesn't appear, contact [Microsoft Customer Service and Support](https://support.microsoft.com/contactus/?ws=support) to obtain the cumulative update package.
72+
73+
</details>
74+
75+
<details>
76+
<summary><b>How to obtain or download this cumulative update package for Windows from Microsoft Update Catalog</b></summary>
77+
78+
The following update is available from the Microsoft Update Catalog:
79+
80+
- :::image type="icon" source="../media/download-icon.png" border="false"::: [Download the cumulative update package for SQL Server 2025 CU1 now](https://www.catalog.update.microsoft.com/Search.aspx?q=KB5074901)
81+
82+
> [!NOTE]
83+
>
84+
> - [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Search.aspx?q=sql%20server%202025) contains this SQL Server 2025 CU and previously released SQL Server 2025 CU releases.
85+
> - This CU is also available through Windows Server Update Services (WSUS).
86+
> - We recommend that you always install the latest cumulative update that is available.
87+
88+
</details>
89+
90+
<details>
91+
<summary><b>How to obtain or download the latest cumulative update package for Linux</b></summary>
92+
93+
To update SQL Server 2025 on Linux to the latest CU, you must first have the [Cumulative Update repository configured](/sql/linux/sql-server-linux-setup#repositories). Then, update your SQL Server packages by using the appropriate platform-specific update command.
94+
95+
For installation instructions and direct links to the CU package downloads, see the [SQL Server 2025 Release Notes](/sql/linux/sql-server-linux-release-notes-2025).
96+
97+
</details>
98+
99+
## File information
100+
101+
<details>
102+
<summary><b>File hash information</b></summary>
103+
104+
You can verify the download by computing the hash of the _?_ TODO file through the following command:
105+
106+
`certutil -hashfile ? SHA256` TODO
107+
108+
| File name | SHA256 hash |
109+
| --------- | ----------- |
110+
| TODO | TODO |
111+
112+
</details>
113+
114+
<details>
115+
<summary><b>Cumulative Update package file information</b></summary>
116+
117+
Download [the list of files that are included in KB5074901](https://download.microsoft.com/download/TODO/KB5074901.csv).
118+
119+
</details>
120+
121+
## Notes for this update
122+
123+
<details>
124+
<summary><b>Prerequisites</b></summary>
125+
126+
To apply this cumulative update package, you must be running SQL Server 2025.
127+
128+
</details>
129+
130+
<details>
131+
<summary><b>Restart information</b></summary>
132+
133+
You might have to restart the computer after you apply this cumulative update package.
134+
135+
</details>
136+
137+
<details>
138+
<summary><b>Registry information</b></summary>
139+
140+
To use one of the hotfixes in this package, you don't have to make any changes to the registry.
141+
142+
</details>
143+
144+
<details>
145+
<summary><b>Important notices</b></summary>
146+
147+
This article also provides the following important information.
148+
149+
### Analysis Services CU build version
150+
151+
Beginning in Microsoft SQL Server 2017, the Analysis Services build version number and SQL Server Database Engine build version number don't match. For more information, see [Verify Analysis Services cumulative update build version](/sql/analysis-services/instances/analysis-services-component-version).
152+
153+
### Cumulative updates (CU)
154+
155+
- Each new CU contains all the fixes that were included with the previous CU for the installed version of SQL Server.
156+
- SQL Server CUs are certified to the same levels as service packs, and should be installed at the same level of confidence.
157+
- We recommend ongoing, proactive installation of CUs as they become available according to these guidelines:
158+
- Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.
159+
- CUs might contain added value over and above hotfixes. This includes supportability, manageability, and reliability updates.
160+
- We recommend that you test SQL Server CUs before you deploy them to production environments.
161+
162+
</details>
163+
164+
<details>
165+
<summary><b>Hybrid environment deployment</b></summary>
166+
167+
When you deploy an update to a hybrid environment (such as Always On, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update:
168+
169+
- [Upgrade a failover cluster instance](/sql/sql-server/failover-clusters/windows/upgrade-a-sql-server-failover-cluster-instance)
170+
171+
> [!NOTE]
172+
> If you don't want to use the rolling update process, follow these steps to apply an update:
173+
>
174+
> - Install the update on the passive node.
175+
> - Install the update on the active node (requires a service restart).
176+
177+
- [Upgrade and update of availability group servers that use minimal downtime and data loss](https://msdn.microsoft.com/library/dn178483.aspx)
178+
179+
> [!NOTE]
180+
> If you enabled Always On together with the **SSISDB** catalog, see the [information about SSIS with Always On](https://techcommunity.microsoft.com/t5/sql-server-integration-services/ssis-with-alwayson/ba-p/388091) about how to apply an update in these environments.
181+
182+
- [How to apply a hotfix for SQL Server in a transactional replication and database mirroring topology](../../database-engine/replication/install-service-packs-hotfixes.md)
183+
- [How to apply a hotfix for SQL Server in a replication topology](../../database-engine/replication/apply-hotfix-sql-replication-topology.md)
184+
- [Upgrading Mirrored Instances](/sql/database-engine/database-mirroring/upgrading-mirrored-instances)
185+
- [Overview of SQL Server Servicing Installation](https://technet.microsoft.com/library/dd638062.aspx)
186+
187+
</details>
188+
189+
<details>
190+
<summary><b>Language support</b></summary>
191+
192+
SQL Server CUs are currently multilingual. Therefore, this CU package isn't specific to one language. It applies to all supported languages.
193+
194+
</details>
195+
196+
<details>
197+
<summary><b>Components (features) updated</b></summary>
198+
199+
One CU package includes all available updates for all SQL Server 2025 components (features). However, the cumulative update package updates only those components that are currently installed on the SQL Server instance that you select to be serviced. If a SQL Server feature (for example, Analysis Services) is added to the instance after this CU is applied, you must reapply this CU to update the new feature to this CU.
200+
201+
</details>
202+
203+
<details>
204+
<summary><b>Support for this update</b></summary>
205+
206+
If other issues occur, or if any troubleshooting is required, you might have to create a service request. The usual support costs will apply to additional support questions and to issues that don't qualify for this specific cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers, or to create a separate service request, go to the [Microsoft support website](https://support.microsoft.com/contactus/?ws=support).
207+
</details>
208+
209+
## How to uninstall this update
210+
211+
<details>
212+
<summary><b>How to uninstall this update on Windows</b></summary>
213+
214+
1. In Control Panel, open the **Programs and Features** item, and then select **View installed updates**.
215+
1. Locate the entry that corresponds to this cumulative update package under **SQL Server 2025**.
216+
1. Press and hold (or right-click) the entry, and then select **Uninstall**.
217+
218+
</details>
219+
220+
<details>
221+
<summary><b>How to uninstall this update on Linux</b></summary>
222+
223+
To uninstall this CU on Linux, you must roll back the package to the previous version. For more information about how to roll back the installation, see [Rollback SQL Server](/sql/linux/sql-server-linux-setup#rollback).
224+
225+
</details>
226+
227+
## References
228+
229+
- [Announcing updates to the SQL Server Incremental Servicing Model (ISM)](/archive/blogs/sqlreleaseservices/announcing-updates-to-the-sql-server-incremental-servicing-model-ism)
230+
- [SQL Server Service Packs are no longer supported starting from SQL Server 2017](https://support.microsoft.com/topic/fd405dee-cae7-b40f-db14-01e3e4951169)
231+
- [Determine which version and edition of SQL Server Database Engine is running](../find-my-sql-version.md)
232+
- [Servicing models for SQL Server](../../general/servicing-models-sql-server.md)
233+
- [Naming schema and Fix area descriptions for SQL Server software update packages](../../database-engine/install/windows/naming-schema-and-fix-area.md)
234+
- [Description of the standard terminology that is used to describe Microsoft software updates](../../../windows-client/deployment/standard-terminology-software-updates.md)

0 commit comments

Comments
 (0)