Here’s the release history for Microsoft SQL Server 2019. Each update is linked to its Microsoft knowledge base article with the download and the list of hotfixes included.
Since SQL Server 2017, we only get Cumulative Updates and GDRs (security fixes), not Service Packs. That makes support end dates a little simpler:
- Mainstream support ends 2025/01/07
- Extended support ends 2030/01/08
| Cumulative Update | Release Date | Build |
|---|---|---|
| CU14* | 2021/11/22 | 15.0.4188.2 |
| CU13* | 2021/10/05 | 15.0.4178.1 |
| CU12* | 2021/08/04 | 15.0.4153.1 |
| CU11 | 2021/06/10 | 15.0.4138.2 |
| CU10 | 2021/04/06 | 15.0.4123.1 |
| CU9 | 2021/02/11 | 15.0.4102.2 |
| GDR | 2021/01/12 | 15.0.4083.2 |
| CU8 | 2020/10/01 | 15.0.4073.23 |
| 2020/09/02 | 15.4063.15 | |
| CU6 | 2020/08/04 | 15.0.4053.23 |
| CU5 | 2020/06/22 | 15.0.4043.16 |
| CU4 | 2020/03/31 | 15.0.4033.1 |
| CU3 | 2020/03/12 | 15.0.4023.6 |
| CU2* | 2020/02/13 | 15.0.4013.40 |
| CU1 | 2020/01/07 | 15.0.4003.23 |
| GDR | 2019/11/04 | 15.0.2070.41 |
| RTM | 2019/11/04 | 15.0.2000.5 |
* Be aware that SQL Server 2019 CU12, CU13, and CU14 have a known issue around Availability Groups automatic seeding. If a database in an Always On availability group has duplicate logical file names, you should either correct that situation or avoid using the automatic seeding functionality after you install those CUs.
* Note that SQL Server 2019 CU7 was removed due to a problem affecting snapshots and CHECKDB.
* Note that SQL Server 2019 CU2 has a known issue where it breaks SQL Server Agent. There’s a little more info in this StackExchange question. If you hit that issue, the official recommendation is to uninstall CU2.