Browse the archive
Microsoft has published KB5126967 for SQL Server 2025, listing CU9 + GDR as a security update with build 17.0.5015.4. The update appeared on Microsoft’s SQL Server update history page with an official release date of October 13, 2026.
Microsoft has published KB5128492 for SQL Server 2025, a GDR security update that advances the build to 17.0.1145.4.
Microsoft has published SQL Server 2022 CU27 + GDR, identified as KB5126934, with build 16.0.4305.5. The update history entry provides the current release details for SQL Server 2022 administrators and developers tracking cumulative and GDR servicing.
Microsoft has added KB5128493, a SQL Server 2022 GDR update, to the update history. The release targets build 16.0.1210.3 and gives administrators a new servicing point to track for SQL Server 2022 systems.
Microsoft has published KB5128494 for SQL Server 2019, identified as CU32 + GDR and carrying build 15.0.4500.2. Here’s the release information now listed in Microsoft’s SQL Server update history.
Microsoft has published a new SQL Server 2019 GDR security update, KB5128495, with build 15.0.2200.2. The release gives administrators a specific new baseline to track in update history and servicing records.
Microsoft has released Cumulative Update 27 for SQL Server 2022 (build 16.0.4295.3). The update brings 42 fixes across engine, backup and restore, replication, Extended Events, Query Store, PolyBase, SQL Agent, and more, while also documenting a few known issues to watch for.
Microsoft has published Cumulative Update 9 for SQL Server 2025, build 17.0.5005.3. The release includes 44 fixes and updates both the Database Engine and Analysis Services, with changes spanning security, replication, Query Store, PolyBase, XML, and more.
Microsoft has released SQL Server 2025 CU8 + GDR (build 17.0.4085.5, KB5122769), a security update that includes 47 fixes across SQL Server Agent, PolyBase, replication, Query Execution, XML, and other engine areas. The release also documents two known issues, including a linked server failure with MSDASQL and an access violation risk during database recovery queries.