Good day guys,
The official announcement of the release of SQL Server 2019 community technology preview 3.1 was published several minutes ago!
Finally we can install the server Side-by-side to previous version (CTP 3.0) which mean that we can compare versions using the same machine. In addition like previous version we can install the server Side-by-side with versions 2017 and older.
No more need to uninstall previous version! Version 3.1 allow In-place upgrade from version 3.0 (not from previous version or 2019), and from older version 2017 and before. If you are following the new version and until now needed to uninstall each version before installing the new one, this is a huge improvement which will save you time.
SQL Server 2019 preview is built with an updated compiler. Before version CTP 3.1 there were issues related to floating point nad getting the right version which is already installed. As of CTP 3.1 release this should work well.
UTF-8 is not supported when the following SQL Server features are in use: (1) In-memory OLTP, (2) External Table for PolyBase, and (3) Always Encrypted (same as previous version 3.0)
>> Always Encrypted protected the data by encrypting it on the client side. This result in limitations on the operations which SQL Server could perform on encrypted data like using different comparing operators. Some operations require using deterministic encryption and some simply were not supported, including any rich computations (for example pattern matching).
A secure enclave is a protected region of memory isolated with a hardware filter which appears as a black box to the rest of processes. Windows Virtualization-based security (VBS) uses the hardware virtualization features to create and isolate a secure region of memory from the normal operating system.
SQL Server 2019 supports Always Encrypted with secure enclaves by getting the column encryption keys from the client driver into the secure enclave. In this case the client driver send to the server encrypted query parameters, and the server can use the clean text since it has the keys encryption keys in the secure enclave (require .NET Framework 4.7.2 in the client side, version 1809 of Windows 10 Enterprise or Windows Server, hardware's support of Virtualization-based security).
Version 3.1 still has issue which Rich computations are pending performance optimizations and error-handling enhancements. This can be workaround by using DBCC traceon(127,-1).
Go and download the new version!