Skip to content

sql-server-ver15-release-notes.md

Latest commit

 

History

History
138 lines (90 loc) · 8.58 KB

sql-server-ver15-release-notes.md

File metadata and controls

138 lines (90 loc) · 8.58 KB
title SQL Server 2019 Release Notes | Microsoft Docs
ms.custom
ms.date 09/24/2018
ms.prod sql-server-2018
ms.reviewer
ms.suite
ms.technology
server-general
ms.tgt_pltfrm
ms.topic article
ms.assetid 13942af8-5a40-4cef-80f5-918386767a47
author MikeRayMSFT
ms.author mikeray
manager craigg
monikerRange = sql-server-ver15 || = sqlallproducts-allversions

SQL Server 2019 preview release notes

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

Note

Preview releases of [!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion]
  • Uninstallation
  • Upgrade from a previous edition of SQL Server

Try [!INCLUDESQL Server 2019]!

CTP 2.0 (September 2018)

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

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

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

Documentation (CTP 2.0)

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

Hardware and software requirements

SQL Graph

Issue and customer impact: Tools which have dependency 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.0.

UTF-8 collations

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] CTP 2.0.

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

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.

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, refer to What's New in SQL Server 2019.

Workaround: No workaround for [!INCLUDESQL Server 2019] CTP 2.0.

Applies to: [!INCLUDESQL Server 2019] CTP 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: [!INCLUDESQL Server 2019] CTP 2.0.

SQL Server Integration Services (SSIS) Transfer Database Task

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.

SQL Server Machine Learning Services installation failure

Issue/Customer impact: SQL Server Machine Learning Services installations fails on machines that have trust relationship issues with the primary domain. The following error will be seen in the logs in this case:

Error: 0 : System.SystemException:The trust relationship between this workstation and the primary domain failed at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) ...

Verify in the logs located at:

  • C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\R_SERVICES\library\RevoScaleR\rxLibs\x64\RegisterRExt.log
  • C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\PYTHON_SERVICES\Lib\site-packages\revoscalepy\rxLibs\RegisterRExt.log Workaround: Resolve the domain trust issues and retry the installation.

Applies to: SQL Server 2019 CTP 2.0.

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

MS_Logo_X-Small