SQL Server 2019 became generally available on November 4th, 2019. Along with it came an important servicing update (GDR1 – 4517790) which should absolutely be installed in every environment. I really wish they could have just made that part of setup, but timing didn't work out; I hope I don't come across any RTM bits at any point in the future. If anything you should be on the latest cumulative update.
In some build lists you may have seen release and build dates published, but something that always felt missing was the internal database version, which can be important because it is impossible to restore a database from a higher db version to a lower one. Database version is indicated below in the DB Version column – helping to makes it clear that you can't take a backup from CTP 3.2 and restore it on CTP 3.0, for example. This internal database version is far less likely to change after GA, but it's possible; the internal database version of the latest builds of SQL Server 2017 is 869, but at GA it was 868. A different topic for a different time.
You can evaluate SQL Server 2019 here. The What's New page has summary information about all the changes, and the Release Notes contain more details and known issues. There are no deprecated engine features and no breaking changes, but there are three database scoped configuration options that have been discontinued. For feature-by-edition breakdowns, see the documentation and this blog post.
| Cumulative Update Train | |||||
| Label | Build # | Date | KB | Fixes (public) | DB Version |
|---|---|---|---|---|---|
| Cumulative Update #18 | 15.0.4261.1 | 2022-09-28 | KB #5016394 | 26 (20) | 904 |
| Cumulative Update #17 | 15.0.4249.2 | 2022-08-11 | KB #5016394 | 43 (38) | 904 |
| Security Update for CU #16 CVE-2022-29143 |
15.0.4236.7 | 2022-06-14 | KB #5014353 Download |
1 | 904 |
| From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index." | |||||
| Cumulative Update #16 | 15.0.4223.1 | 2022-04-18 | KB #5011644 | 47 (41) | 904 |
| ⚠️ Be aware of a change to TDE-compressed backups, which won't restore to previous CUs. Brent Ozar has some details. | |||||
| Cumulative Update #15 | 15.0.4198.2 | 2022-01-27 | KB #5008996 | 39 (35) | 904 |
| Cumulative Update #14 | 15.0.4188.2 | 2021-11-22 | KB #5007182 | 38 (33) | 904 |
| Cumulative Update #13 | 15.0.4178.1 | 2021-10-05 | KB #5005679 | 38 (19) | 904 |
| ⚠️ Please use caution if you use AGs with automatic seeding. Info still coming out, but seems there is an issue introduced with CU12 (and still present in CU13) that breaks automatic seeding. Twitter thread. | |||||
| Cumulative Update #12 | 15.0.4153.1 | 2021-08-04 | KB #5004524 | 40 (29) | 904 |
| ⚠️ Please use caution if you use AGs with automatic seeding. Info still coming out, but seems there is an issue introduced with CU12 (and still present in CU13) that breaks automatic seeding. Twitter thread. | |||||
| Cumulative Update #11 | 15.0.4138.2 | 2021-06-10 | KB #5003249 | 62 (35) | 904 |
| Cumulative Update #10 | 15.0.4123.1 | 2021-04-06 | KB #5001090 | 63 (39) | 904 |
| Cumulative Update #9 | 15.0.4102.2 | 2021-02-11 | KB #5000642 | 140 (89) | 904 |
| Security Update for CU #8 CVE-2021-1636 |
15.0.4083.2 | 2021-01-12 | KB #4583459 | 1 | 904 |
This security update addresses an escalation of privilege vulnerability described in CVE-2021-1636. It is also being pushed via Windows Update, so you may get this sooner than you expect it. |
|||||
| Cumulative Update #8 | 15.0.4073.23 | 2020-10-01 | KB #4577194 | 104 (81) | 904 |
| Cumulative Update #7 | 15.0.4063.15 | 2020-09-02 | KB #4570012 | 904 | |
| ⚠️ Please do not download. Microsoft has discovered an issue involving snapshots/CheckDB, and pulled this CU as a result; for more info, see Cumulative Update #7 for SQL Server 2019 RTM (Removed) and Avoid SQL Server 2019 Cumulative Update #7. If you don't feel safe moving to CU8 (and who could blame you at this point), you can still get CU6 from the Microsoft Update Catalog. | |||||
| Cumulative Update #6 | 15.0.4053.23 | 2020-08-04 | KB #4563110 | 51 (42) | 904 |
| Cumulative Update #5 | 15.0.4043.16 | 2020-06-22 | KB #4552255 | 86 (58) | 904 |
| Cumulative Update #4 | 15.0.4033.1 | 2020-03-31 | KB #4548597 | 50 (38) | 904 |
| Cumulative Update #3 | 15.0.4023.6 | 2020-03-12 | KB #4538853 | 56 (11) | 904 |
| Cumulative Update #2 | 15.0.4013.40 | 2020-02-13 | KB #4536075 | 134 (88) | 904 |
| Cumulative Update #1 | 15.0.4003.23 | 2020-01-07 | KB #4527376 | 83 (62) | 904 |
| GDR Train | |||||
| Label | Build # | Date | KB | Fixes (public) | DB Version |
| GDR Security Update CVE-2022-29143 |
15.0.2095.3 | 2022-06-14 | KB #5014356 Download |
1 | 904 |
| From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index." | |||||
| GDR Security Update CVE-2021-1636 |
15.0.2080.9 | 2021-01-12 | KB #4583458 | 1 | 904 |
This security update addresses an escalation of privilege vulnerability described in CVE-2021-1636. It is also being pushed via Windows Update, so you may get this sooner than you expect it. |
|||||
| GDR1 | 15.0.2070.41 | 2019-11-04 | KB #4517790 | 1 | 904 |
| RTM / GA | 15.0.2000.5 | 2019-11-04 | 904 | ||
| Pre-RTM Releases | |||||
| Label | Build # | Date | DB Version | ||
| RC1.1 Refresh | 15.0.1900.47 | 2019-08-29 | 904 | ||
| RC1 | 15.0.1900.25 | 2019-08-01 | 904 | ||
| CTP 3.2 | 15.0.1800.32 | 2019-07-24 | 904 | ||
| CTP 3.1 | 15.0.1700.37 | 2019-06-26 | 902 | ||
| CTP 3.0 | 15.0.1600.8 | 2019-05-17 | 902 | ||
| CTP 2.5 | 15.0.1500.28 | 2019-04-15 | 897 | ||
| CTP 2.4 | 15.0.1400.75 | 2019-03-16 | 897 | ||
| CTP 2.3 | 15.0.1300.359 | 2019-02-15 | 897 | ||
| CTP 2.2 | 15.0.1200.24 | 2018-12-05 | 896 | ||
| CTP 2.1 | 15.0.1100.94 | 2018-11-01 | 896 | ||
| CTP 2.0 | 15.0.1000.34 | 2018-09-18 | 895 | ||
