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.
|Label||Build #||Date||KB||Fixes (public)||DB Version|
|Cumulative Update #8||15.0.4073.23||2020-10-01||KB #4577194||74 (74)||904|
|This was released out-of-band in response to Cumulative Update #7, which was pulled due to a snapshot/CheckDB issue. Not a lot of detail, unfortunately, in the KB article or in this blog post.|
|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; 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|
|RTM / GA||15.0.2000.5||2019-11-04||904|
|Label||Build #||Date||DB Version|