Merge pull request #7829 from pmasl/patch-330

Update what-s-new-in-sql-server-ver15.md

Author: PRMerger9

docs/sql-server/what-s-new-in-sql-server-ver15.md

@@ -102,6 +102,7 @@ Continue reading for more details about these features.
 [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] introduces or enhances the following new features for the Database Engine
 
 ### Scalar UDF inlining (CTP 2.1)
+
 Scalar UDF inlining automatically transforms scalar user-defined functions (UDF) into relational expressions and embeds them in the calling SQL query, thereby improving the performance of workloads that leverage scalar UDFs. Scalar UDF inlining facilitates cost-based optimization of operations inside UDFs, and results in efficient plans that are set-oriented and parallel as opposed to inefficient, iterative, serial execution plans. This feature is enabled by default under database compatibility level 150.
 
 ### Improve truncation message for ETL DW scenarios (CTP 2.1)
@@ -110,15 +111,15 @@ The error message ID 8152 `String or binary data would be truncated` is familiar
 
 `String or binary data would be truncated in table '%.*ls', column '%.*ls'. Truncated value: '%.*ls'.`
 
-The new default error message provides more context for the data truncation problem, simplifying the troubleshooting process. If existing applications rely on parsing message ID 8152 and cannot handle the new message ID 2628, then you can revert back to using message ID 8152, by enabling trace flag 459.
+The new error message 2628 provides more context for the data truncation problem, simplifying the troubleshooting process. For CTP 2.1, this is an opt-in error message and requires [trace flag](../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md) 460 to be enabled.
 
-### UTF-8 support (CTP 2.0)
+### UTF-8 support (CTP 2.1)
 
-Added support for UTF-8 collations in [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] CTP 2.1 Setup.
+Added support to select UTF-8 collations as server collation during [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] CTP 2.1 Setup.
 
 ### Database compatibility level (CTP 2.0)
 
-Database **COMPATIBILITY_LEVEL 150** is added. To enable for a specific user database, execute: (CTP 2.0)
+Database **COMPATIBILITY_LEVEL 150** is added. To enable for a specific user database, execute:
 
    ```sql
    ALTER DATABASE database_name SET COMPATIBILITY_LEVEL =  150;
@@ -130,7 +131,7 @@ Full support for the widely used UTF-8 character encoding as an import or export
 
 For example,`LATIN1_GENERAL_100_CI_AS_SC` to `LATIN1_GENERAL_100_CI_AS_SC_UTF8`. UTF-8 is only available to Windows collations that support supplementary characters, as introduced in SQL Server 2012. `NCHAR` and `NVARCHAR` allow UTF-16 encoding only, and remain unchanged.
 
-This feature may provide significant storage savings, depending on the character set in use. For example, changing an existing column data type with ASCII strings from `NCHAR(10)` to `CHAR(10)` using an UTF-8 enabled collation, translates into nearly 50% reduction in storage requirements. This reduction is because `NCHAR(10)` requires 22 bytes for storage, whereas `CHAR(10)` requires 12 bytes for the same Unicode string.
+This feature may provide significant storage savings, depending on the character set in use. For example, changing an existing column data type with Latin strings from `NCHAR(10)` to `CHAR(10)` using an UTF-8 enabled collation, translates into nearly 50% reduction in storage requirements. This reduction is because `NCHAR(10)` requires 22 bytes for storage, whereas `CHAR(10)` requires 12 bytes for the same Unicode string.
 
 ### Resumable online index create (CTP 2.0)