| title | Scalability | Microsoft Docs |
|---|---|
| ms.custom | |
| ms.date | 08/27/2015 |
| ms.prod | sql |
| ms.prod_service | database-engine, sql-database |
| ms.reviewer | |
| ms.technology | in-memory-oltp |
| ms.topic | conceptual |
| ms.assetid | a4891c57-56bb-49f4-9bb5-f11b745279e5 |
| author | MightyPen |
| ms.author | genemi |
| monikerRange | =azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDEappliesto-ss-asdb-xxxx-xxx-md] [!INCLUDEssSQL15] contains scalability enhancements to the on-disk storage for memory-optimized tables.
[!INCLUDEssSQL14] had a single offline checkpoint thread that scanned the transaction log for changes to memory-optimized tables and persisted them in checkpoint files (such as data and delta files). In machines with a larger number of cores, the single offline checkpoint thread could fall behind.
Starting with [!INCLUDEssSQL15], there are multiple concurrent threads responsible to persist changes to memory-optimized tables.
In the previous release of [!INCLUDEssNoVersion], the log apply as part of recovery operation was single threaded. Starting with [!INCLUDEssSQL15], the log apply is multi-threaded.
The MERGE operation is now multi-threaded.
Note
Manual Merge has been disabled as multi-threaded merge is expected to keep up with the load.
The DMVs sys.dm_db_xtp_checkpoint_stats (Transact-SQL) and sys.dm_db_xtp_checkpoint_files (Transact-SQL) have been changed significantly.
The In-memory OLTP engine continues to use memory-optimized filegroup based on FILESTREAM, but the individual files in the filegroup are decoupled from FILESTREAM. These files are fully managed (such as for create, drop, and garbage collection) by the In-Memory OLTP engine.
Note
DBCC SHRINKFILE (Transact-SQL) is not supported.
Creating and Managing Storage for Memory-Optimized Objects
Database Files and Filegroups
ALTER DATABASE File and Filegroup Options (Transact-SQL)