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:

Note

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

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

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

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

Documentation (CTP 2.3)

  • 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 (CTP 2.3)

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.3 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.3, 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

    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 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.3, 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.3, 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.3, 2.2, CTP 2.1, 2.0.

System Dynamic Management Views

SQL Server Analysis Services (SSAS)

  • Issue and customer impact: For tabular models with dynamic security, under some circumstances a user can see data from another user belonging to the same role.

    Scenario: There are at least 2 roles in the model. One of the roles doesn't have any dynamic security expression that contains USERNAME or USERPRINCIPALNAME. The second role with dynamic row-level security is defined for user A and user B by using expressions that contain USERNAME or USERPRINCIPLENAME. User A and user B can connect and query data, however, user B may see data secured only for user A under certain circumstances.

  • Workaround: Add a dummy measure in the model. For example [DummyMeasure] := UserName(). This ensures that dynamic expressions are evaluated for the row level security expressions.

  • Applies to: SQL Server 2019 preview CTP 2.3.

info_tip Get Help

MS_Logo_X-Small