SQL Server 2019 preview release notes

THIS TOPIC APPLIES TO:yesSQL Server (starting with 2019)noAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

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


Preview releases of SQL Server are made available for you to experience the features of the upcoming release. They are not supported or licensed for production use. The following scenarios are explicitly unsupported:

  • Side-by-side installation with other versions of SQL Server
  • Upgrade an existing instance of SQL Server from any version

Try SQL Server 2019 preview!

CTP 2.2 (December 2018)

SQL Server 2019 preview CTP 2.2 is the latest public release of SQL Server 2019 preview.

SQL Server 2019 preview CTP 2.2 is available only as Evaluation Edition. No other editions are available. Support for CTP 2.2 is described in license_Eval.rtf with your installation media.

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

Documentation (CTP 2.2)

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

Hardware and software requirements

Updated compiler

  • Issue and customer impact: SQL Server 2019 preview 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 CTP 2.2 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: SQL Server 2019 CTP 2.2, CTP 2.1

SQL Server Integration Services (SSIS) page deployment after switching DB to single-user mode and then switching back

  • Issue and customer impact: After SSISDB 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.2, CTP 2.1

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:

    • Linked Server
    • In-memory OLTP
    • External Table for PolyBase


    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 supports choice of UTF-8 enabled collations in the UI.

  • Workaround: No workaround for SQL Server 2019 preview CTPs.

  • Applies to: SQL Server 2019 preview CTP 2.2, CTP 2.1, CTP 2.0.

SQL Graph

  • 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 SQL Server Management Studio may not work.

  • Workaround: Writing Transact-SQL scripts and running them against the server using SQL Server Management Studio 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 Transact-SQL scripts.

  • Applies to: SQL Server 2019 preview CTP 2.2, CTP 2.1, 2.0.

Always Encrypted with secure enclaves

  • 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: SQL Server 2019 preview CTP 2.2, CTP 2.1, 2.0.

CTP 2.1 (October 2018)

SQL Server 2019 preview CTP 2.1 is the previous public release of SQL Server 2019 preview.

UDF Inlining

  • 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

SQL Server Integration Service - Fuzzy Lookup Transformation

  • 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: SQL Server 2019 preview CTP2.1

Lightweight query profiling infrastructure

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


    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 SQL Server 2019 preview CTPs.

  • Applies to: SQL Server 2019 preview CTP 2.1 and CTP 2.0.

info_tip Get Help