SQL Server 2019 preview release notes

THIS TOPIC APPLIES TO:yesSQL Server noAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

This article describes limitations and known issues for the SQL Server 2019. For related information, see:

What's New in SQL Server 2019

Note

The content is published for the SQL Server 2019 release candidate. The release candidate is pre-release software. The information is subject to change. For information about support scenarios, refer to Support.

SQL Server 2019 release candidate (RC)

SQL Server 2019 RC is the latest public release of SQL Server 2019.

SQL Server 2019 RC is available only as Evaluation Edition. No other editions are available.

Complete details about support and licensing for release candidate software are in license_Eval.rtf with your installation media.

Enabled deployment scenarios

SQL Server 2019 release candidate (RC) enables the following scenarios:

  • Side-by-side installation. Install instances of SQL Server 2019 RC with instances of SQL Server 2012 through SQL Server 2017, or other instances SQL Server 2019 CTP 3.0 or higher.

    Note

    While side-by-side is not blocked with SQL Server 2008 and 2008 R2, there are no commonly supported Windows Operating system versions between them and SQL Server 2019.

  • In-place upgrade. Upgrade to SQL Server 2019 RC from instances of SQL Server 2012 through SQL Server 2017 and SQL Server CTP 3.0. Upgrade from a SQL Server 2019 CTP below 3.0 is not supported, a new installation must be performed.

    Note

    While in-place upgrade from SQL Server 2008 and 2008 R2 is not blocked, there are no commonly supported Windows Operating system versions between them and SQL Server 2019.

Support

SQL Server 2019 RC is preview software. It is not publicly supported for operations. Customers who are in the SQL Early Adopter Program, may have support to run SQL Server 2019 RC by special agreement, in consultation with Microsoft.

Limited support for customers not in the early adoption program may be found at one of the following locations:

Try SQL Server 2019!

Documentation

  • Issue and customer impact: Documentation for SQL Server 2019 (15.x) is limited and content is included with the SQL Server 2017 (14.x) documentation set. Content in articles that is specific to SQL Server 2019 (15.x) is noted with Applies to.

  • Issue and customer impact: SQL Server documentation can be filtered by version. Use the control at the top left of each documentation page to filter for your requirements.

  • Issue and customer impact: No offline content is available for SQL Server 2019 (15.x).

Build number

The build number for SQL Server 2019 RC on Windows, Linux, and containers is 15.0.1900.25. The build number for SQL Server 2019 RC used in big data clusters is 15.0.1900.47.

Hardware and software requirements

Features excluded from support

  • Issue and customer impact: SQL Server 2019 excludes support for the following components, features, and scenarios:

    • SQL Server Analysis Services
    • SQL Server Reporting Services
    • Always On availability groups on Kubernetes
  • Workaround: None. Exclusion applies to all customers, including participants in SQL Early Adopter Program.

  • Applies to: Release candidate

Updated compiler

  • Issue and customer impact: SQL Server 2019 is built with an updated compiler. CTP 2.1 had a known issue where results for floating point and other conversion scenarios may have returned a different value than previous versions because of the updated compiler. CTP 2.2 includes work to ensure that the affected scenarios return the same results as previous versions of SQL Server. As of the release candidate release we do not know any remaining issues. Please report any result anomalies compared to SQL Server 2017 (14.x) to SQL Server team immediately.

  • Workaround: N/A

  • Applies to: Release candidate

Installation Wizard may wait between EULA pages

  • Issue and customer impact: During installation with Installation Wizard, the process may wait an extended amount of time between the end user license agreement (EULA) for R Services and the EULA for Python.

  • Workaround: Wait for the Installation Wizard to proceed. The time to wait may exceed 30 minutes.

  • Applies to: SQL Server 2019 CTP 3.0

UTF-8 collations

  • Issue and customer impact: UTF-8 enabled collations cannot be used with some other SQL Server features. UTF-8 is not supported when the following SQL Server features are in use:

    • In-memory OLTP
    • External Table for PolyBase (SQL Server 2019 RC 1)
    • Always Encrypted (Up to SQL Server 2019 RC 1)
    • Linked Servers (up to SQL Server 2019 CTP 3.2)

    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 SQL Server Management Studio (SSMS) version 18 supports choice of UTF-8 enabled collations in the UI.

  • Workaround: No workaround for SQL Server 2019 CTPs.

  • Applies to: All CTP releases.

Always Encrypted with secure enclaves

  • Issue and customer impact: Rich computations are pending performance optimizations and error-handling enhancements, and are currently disabled by default.

  • Workaround: To enable rich computations, run DBCC traceon(127,-1). For details, see Enable rich computations.

  • Applies to: SQL Server 2019 CTP 3.2, CTP 3.1

SQL Server Configuration Manager may not start

  • Issue and customer impact: SQL Server Configuration Manager (SSCM) does not start on a machine without VCRuntime 140. When starting SSCM, the user may see the following dialog:

    MMC could not create the snap-in. The snap-in might not have been installed correctly.

  • Workaround: Install the latest VC Runtime 2013 (x86):

  • Applies to: SQL Server 2019 CTP 3.1, CTP 3.0, CTP 2.5.

Always On Availability Group Kubernetes operator not supported

  • Issue and customer impact: The Kubernetes operator for Always On Availability Groups is not supported in this release candidate and will not be available at RTM.

  • Workaround: None

  • Applies to: SQL Server 2019 Release candidate

  • 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: SQL Server 2019 release candidate.

info_tip Get Help

MS_Logo_X-Small