title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | monikerRange |
---|---|---|---|---|---|---|---|---|
SQL Server 2019 release notes |
Find information about SQL Server 2019 (15.x) limitations, known issues, help resources, and other release notes. |
MikeRayMSFT |
mikeray |
11/04/2019 |
sql |
release-landing |
release-notes |
>= sql-server-2016 |
[!INCLUDESQL Server 2019]
This article describes limitations and known issues for the [!INCLUDESQL Server 2019]. For related information, see:
[What's New in [!INCLUDESQL Server 2019]](../sql-server/what-s-new-in-sql-server-ver15.md)
[!INCLUDEsql-server-2019]
[!INCLUDESQL Server 2019] is the latest public release of [!INCLUDESQL Server 2019].
Complete details about licensing are in License Terms
folder on the installation media.
- Issue and customer impact: [!INCLUDEssNoVersion] documentation can be filtered by version. Use the control at the top left of each documentation page to filter for your requirements.
The RTM build number for SQL Server 2019 is 15.0.2000.5
.
[!INCLUDE sql-server-servicing-updates-version-15]
This section identifies known issues you may experience with this product.
-
Issue and customer impact: [!INCLUDESQL Server 2019] installation fails when the following installations happen in this order:
- SQL Server Management Studio (SSMS) version 18.0, 18.1, 18.2, or 18.3 is installed on the server.
- [!INCLUDESQL Server 2019] installation is attempted from removable media. For example, the installation media is a DVD.
-
Workaround:
- Uninstall any version of SSMS older than SSMS 18.3.1.
- Install a newer version of SSMS (18.3.1 or later). For the latest version, see Download SSMS.
- Install [!INCLUDESQL Server 2019] normally.
-
Applies to: [!INCLUDESQL Server 2019]
-
Issue and customer impact: UTF-8 enabled collations cannot be used with the following features:
- In-Memory OLTP tables
- Always Encrypted with Secure Enclaves (When not using Secure Enclaves, Always Encrypted can use UTF-8)
[!WARNING] Creating a bacpac of a database containing table columns defined as CHAR or VARCHAR that use more than 4000 bytes will fail.
[!NOTE] There is currently no UI support to choose UTF-8 enabled collations in Azure Data Studio or SQL Server Data Tools (SSDT). The latest [!INCLUDEssManStudioFull] (SSMS) version 18 supports choice of UTF-8 enabled collations in the UI.
-
Applies to: [!INCLUDESQL Server 2019] RTM
-
Issue and customer impact: The notification email from Master Data Services (MDS) contains a broken link. The link navigates to a page that returns an error like the following message:
The view 'Index' or its master was not found or no view engine supports the searched locations.
-
Workaround: Open the MDS portal and go to the resource manually.
-
Applies to: [!INCLUDESQL Server 2019] RTM
For issues in SQL Server Machine Learning Services, see Known issues in SQL Server Machine Learning Services.
[!INCLUDEget-help-options-msft-only]