You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/sql-server/what-s-new-in-sql-server-ver15.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ Continue reading for more details about these features.
108
108
- Pause an ongoing index create operation and resume it later allowing to temporarily free system resources as required and resume this operation later.
109
109
- Create large indexes without using a lot of log space and a long-running transaction that blocks other maintenance activities and allowing log truncation.
110
110
111
-
In case of an execution error or failure, without this feature an online index create operation must be executed again and the operation must be restarted from the beginning.
111
+
In case of an index create failure, without this feature an online index create operation must be executed again and the operation must be restarted from the beginning.
112
112
113
113
With this release, we extend the resumable functionality adding this feature to available [resumable online index rebuild](http://azure.microsoft.com/blog/modernize-index-maintenance-with-resumable-online-index-rebuild/).
114
114
@@ -162,10 +162,6 @@ This may provide significant storage savings, depending on the character set in
162
162
The lightweight query profiling infrastructure (LWQPI) is now enabled by default. The lightweight query profiling infrastructure was introduced in SQL Server 2016 SP1. It offers a query execution statistics collection mechanism with an expected overhead of 2% CPU, compared with an overhead of up to 75% CPU for the standard query profiling mechanism. On previous versions,
163
163
it was OFF by default. Database administrators could enable it with [trace flag 7412](../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md).
164
164
165
-
### Expanded support for Persistent Memory (PMEM) devices
166
-
167
-
Any SQL Server file (database files, transaction log files, In-Memory OLTP checkpoint files, etc) placed on a Persistent Memory device (PMEM, also known as Storage Class Memory or SCM) will operate in "enlightened" mode, where SQL Server will directly access the device, avoiding the storage stack of the operating system and allowing extreme low latency I/Os against such devices.
168
-
169
165
### Data Discovery and Classification
170
166
171
167
Data discovery and classification provides advanced capabilities natively built into SQL Server for classifying, labeling, and protecting the sensitive data in your databases. Classifying your most sensitive data (business, financial, healthcare, PII, etc.) can play a pivotal role in your organizational information protection stature. It can serve as infrastructure for:
@@ -249,7 +245,7 @@ For detailed information, see [What's new in SQL Server Machine Learning Service
249
245
250
246
Configure replication SQL Server Management Studio (SSMS) or use [replication stored procedures](../relational-databases/system-stored-procedures/replication-stored-procedures-transact-sql.md).
251
247
252
-
-**Support for the Microsoft Distributed Transaction Coordinator (MSDTC)**: SQL Server 2019 on Linux supports the Microsoft Distributed Transactions Coordinator (MSDTC).
248
+
-**Support for the Microsoft Distributed Transaction Coordinator (MSDTC)**: SQL Server 2019 on Linux supports the Microsoft Distributed Transaction Coordinator (MSDTC). For details, see [How to configure MSDTC on Linux](../linux/sql-server-linux-configure-msdtc.md).
253
249
254
250
-**Always On Availability Group on Docker containers with Kubernetes**: Kubernetes can orchestrate containers running SQL Server instances to provide a highly available set of databases with SQL Server Always On Availability Groups. A Kubernetes operator deploys a StatefulSet including a container with **mssql-server container** and a health monitor.
255
251
@@ -261,6 +257,9 @@ For detailed information, see [What's new in SQL Server Machine Learning Service
261
257
262
258
-**New RHEL-based container images**: New certified RHEL-based container images are now available.
263
259
260
+
-**Expanded support for Persistent Memory (PMEM) devices**: Any SQL Server file (database files, transaction log files, In-Memory OLTP checkpoint files, etc) placed on a Persistent Memory device (PMEM, also known as Storage Class Memory or SCM) will operate in "enlightened" mode, where SQL Server will directly access the device, avoiding the storage stack of the operating system and allowing extreme low latency I/Os against such devices.
261
+
262
+
264
263
## <aid="polybase"></a> PolyBase
265
264
266
265
-**New connectors for SQL Server, Oracle, Teradata, and MongoDB**: SQL Server 2019 introduces new connectors to external data for SQL Server, Oracle, Teradata, and MongoDB.
0 commit comments