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

Try [!INCLUDESQL Server 2019]!

• [Download [!INCLUDESQL Server 2019] to install on Windows](http://go.microsoft.com/fwlink/?LinkID=862101)
• Install on Linux for Red Hat Enterprise Server, SUSE Linux Enterprise Server, and Ubuntu.
• Run on SQL Server 2019 on Docker.

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

[!INCLUDESQL Server 2019] CTP 2.1 is available only as Evaluation Edition. No other editions are available. Support for CTP 2.1 is described in license_Eval.rtf with your installation media.

Limited support may be found at one of the following locations:

• Forums

  • SQL Server Feedback
  • Getting started with SQL Server
  • Transact-SQL
  • SQL Server Documentation

• Or tweet @SQLServer with #sqlhelp

• 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: SQL Server 2019 preview uses an updated compiler to build SQL Server. In some cases code compiled with the new compiler can return floating point numeric values that are different from previous versions of SQL Server. Behavior change will be restricted to new compatibility level (150) in a future CTP.

• Workaround: N/A

• Applies to: SQL Server 2019 CTP 2.1

• Issue and customer impact: After SSISB is switched from single-user mode back to multi-user mode, the following error may be reported when deploying a package:

  Cannot continue the execution because the session is in the kill state.

• Workaround: Stop and restart the SQL Server instance and switch SSISDB back to multi-user mode.

• Applies to: SQL Server 2019 preview CTP 2.1

• Issue and customer impact: There are corner case scenarios where nested calls to user defined functions inline do not correctly validate security.

• Workaround: Disable UDF inlining for such UDFs using the INLINE = OFF setting.

• Applies to: SQL Server 2019 CTP 2.1

• Issue and customer impact: Executing the command ALTER DATABASE SCOPED CONFIGURATION SET LIGHTWEIGHT_QUERY_PROFILING = ON returns a syntax error. Any scenarios that depend on executing this command will fail.

  [!NOTE] Currently, the lightweight query profiling infrastructure (LWP) cannot be controlled at the individual database level, and remains enabled for all databases by default. For more information on LWP, see What's New in SQL Server 2019.

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

• Applies to: [!INCLUDESQL Server 2019] CTP 2.1 and CTP 2.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:

  • SQL Server Replication

  • Linked Server

  • In-memory OLTP

  • External Table for PolyBase

    Also note there is currently no UI support to choose UTF-8 enabled collations in Azure Data Studio or SSDT. The latest SSMS version supports choice of UTF-8 enabled collations in the UI.

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

• Applies to: [!INCLUDESQL Server 2019] CTP 2.1, CTP 2.0.

• Issue and customer impact: Tools that are dependent on DacFx like import-export, will not work for the new graph features - Edge Constraints or Merge DML. Scripting in [!INCLUDEssManStudioFull] may not work.

• Workaround: Writing [!INCLUDEtsql] scripts and running them against the server using [!INCLUDEssManStudioFull] or SQLCMD will work. Exporting or Importing database objects that create Edge constraints, have the new merge DML syntax, or create derived tables/views on graph objects will not work. Users will have to manually create such objects in their database using [!INCLUDEtsql] scripts.

• Applies to: [!INCLUDESQL Server 2019] CTP 2.1, 2.0.

• Issue and customer impact: Rich computations are pending several performance optimizations, include limited functionality (no indexing, etc.), 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 2.1, 2.0.

• Issue / customer impact: The Fuzzy Lookup Transformation would fail with following error if it's set to reuse index:

  The specified delimiters do not match the delimiters used to build the pre-existing match index "...". This error occurs when the delimiters used to tokenize fields do not match. This can have unknown effects on the matching behavior or results.

• Workaround: N/A

• More information: N/A

• Applies To: [!INCLUDESQL Server 2019] CTP2.1

[!INCLUDESQL Server 2019] CTP 2.0 is the first public release of [!INCLUDESQL Server 2019].

• Issue and customer impact: When a Transfer Database Task is configured to transfer a database in Database Online mode, it may fail with the following error:

  The Execute method on the task returned error code 0x80131500 (An error occurred while transferring data. See the inner exception for details.). The Execute method must succeed, and indicate the result using an "out" parameter.

• Workaround: Execute DBCC TRACEON (7416,-1) on the server and try again.

• Applies to: [!INCLUDESQL Server 2019] CTP 2.0.

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