How to configure persistent memory (PMEM) for SQL Server on Linux

APPLIES TO: yesSQL Server (Linux only) noAzure SQL Database noAzure SQL Data Warehouse noParallel Data Warehouse

This article describes how to configure the persistent memory (PMEM) for SQL Server on Linux. PMEM support on Linux was introduced in SQL Server 2019 preview.


SQL Server 2016 introduced support for Non-Volatile DIMMs, and an optimization called Tail of the Log Caching on NVDIMM. These optimizations reduced the number of operations needed to harden a log buffer to persistent storage. This leverages Windows Server direct access to a persistent memory device in DAX mode.

SQL Server 2019 preview extends the support for persistent memory (PMEM) devices to Linux, providing full enlightenment of data and transaction log files placed on PMEM. Enlightenment refers to the method of access to the storage device using efficient user-space memcpy() operations. Rather than going through the file system and storage stack, SQL Server leverages DAX support on Linux to directly place data into devices, which reduces latency.

Enable enlightenment of database files

To enable enlightenment of database files in SQL Server on Linux, follow the following steps:

  1. Configure the devices.

In Linux, use the ndctl utility.

  • Install ndctl to configure PMEM device. You can find it here.
  • Use [ndctl] to create a namespace.
ndctl create-namespace -f -e namespace0.0 --mode=fsdax* --map=mem


If you are using ndctl version lower than 59, use --mode=memory.

Use ndctl to verify the namespace. Sample output follows:

ndctl list
  • Create and mount PMEM device

    For example, with XFS

    mkfs.xfs -f /dev/pmem0
    mount -o dax,noatime /dev/pmem0 /mnt/dax
    xfs_io -c "extsize 2m" /mnt/dax

    For example, with EXT4

    mkfs.ext4 -b 4096 -E stride=512 -F /dev/pmem0
    mount -o dax,noatime /dev/pmem0 /mnt/dax

Once the device has been configured with ndctl, formatted and mounted, you can place database files in it. You can also create a new database

  1. Since PMEM devices are O_DIRECT safe, enable trace flag 3979 to disable the forced flush mechanism. This trace flag is a startup trace flag, and as such needs to be enabled using the mssql-conf utility. Please note that this is a server-wide configuration change, and you should not use this trace flag if you have any O_DIRECT non-compliant devices that need the forced flush mechanism to ensure data integrity. For more information see

  2. Restart SQL Server.

Next steps

For more information about SQL Server on Linux, see SQL Server on Linux.