[!INCLUDEtsql-appliesto-ssver15-xxxx-xxxx-xxx]

This article describes limitations and known issues for the [!INCLUDESQL Server 2019] Community Technology Preview (CTP) releases. For related information, see:

• What's New in SQL Server 2019

[!INCLUDESQL Server 2019] CTP 3.2 is the latest public release of [!INCLUDESQL Server 2019].

[!INCLUDESQL Server 2019] CTP 3.2 is available only as Evaluation Edition. No other editions are available.

Complete details about support and licensing for CTP releases are in license_Eval.rtf with your installation media.

[!INCLUDEctp-support-exclusion]

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

• 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.

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

• Issue and customer impact: Hardware and software requirements are still being reviewed and not final for the product release.

  • Hardware
    • Windows - processor, memory, and operating system requirements
    • Linux - system requirements
  • Software
    • Windows Server 2016 or later. For additional requirements, see Requirements for Installing SQL Server
    • Microsoft .NET Framework 4.6.2. Available from Download Center.
    • For Linux, refer to Linux - supported platforms

• Issue and customer impact: [!INCLUDESQL 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
  • Accelerated database recovery

• Workaround: None. Exclusion applies to all customers, including participants in SQL Early Adopter Program.

• Applies to: All CTP releases

• Issue and customer impact: [!INCLUDESQL 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 [!INCLUDEssNoVersion]. As of CTP 3.2 release we do not know any remaining issues. Please report any result anomalies compared to [!INCLUDEss2017] to [[!INCLUDEssNoVersion] team](http://aka.ms/sqlfeedback) immediately.

• Workaround: N/A

• Applies to: All CTP releases

• Issue and customer impact: During installation with Installation Wizard, the process may wait an excessive 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

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

  • In-memory OLTP
  • External Table for PolyBase
  • Always Encrypted

  [!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.

• Workaround: No workaround for [!INCLUDESQL Server 2019] CTPs.

• Applies to: [!INCLUDESQL Server 2019] CTP 3.1, CTP 3.0, CTP 2.5, CTP 2.4, CTP 2.3, CTP 2.2, CTP 2.1, CTP 2.0.

• 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: [!INCLUDESQL Server 2019] CTP 3.1

• 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):

  • Verbose
  • Direct

• Applies to: [!INCLUDESQL Server 2019] CTP 3.1, CTP 3.0, CTP 2.5.

[!INCLUDEget-help-options-msft-only]