Full 64-bit SQL Server Express supports In-Memory OLTP, but LocalDB does not, and Express has a 352 MB memory-optimized data limit per database. Verify the actual instance before troubleshooting a CREATE TABLE ... MEMORY_OPTIMIZED error.
Last updated: November 6, 2026.
SELECT
SERVERPROPERTY('Edition') AS edition,
SERVERPROPERTY('ProductVersion') AS product_version,
SERVERPROPERTY('IsXTPSupported') AS xtp_supported,
@@SERVICENAME AS service_name;
SELECT name, type_desc, physical_name
FROM sys.database_files
ORDER BY file_id;xtp_supported = 1 confirms that the connected Database Engine instance can use In-Memory OLTP. The edition and service name also reveal accidental LocalDB or wrong-instance connections. Run this query through the same connection string used by the application.
Check edition limits and prerequisites
Microsoft’s In-Memory OLTP requirements state that SQL Server 2016 SP1 and later support the feature in every edition. Express is limited to 352 MB of memory-optimized data per database and requires the 64-bit engine, sufficient RAM and disk, and a processor with cmpxchg16b.
The SQL Server 2022 feature matrix lists In-Memory OLTP for Express but excludes the LocalDB installation option. SSMS is only a client, so installing a newer SSMS does not add features to the Database Engine service you connected to.
Create the storage in the right order
A durable memory-optimized table needs a database with a MEMORY_OPTIMIZED_DATA filegroup and at least one container. Put that container on storage accessible to the SQL Server service account. Confirm the directory exists and that the service identity—not your Windows login—can create files there.
Create the filegroup and container first, then create a small test table with a primary key and a memory-optimized index. Use an empty test database before adapting a production database. If the support flag is zero, changing table syntax will not help; connect to the full Express service or install a supported 64-bit instance.
Watch the 352 MB quota and available system memory during tests. Continue with verifying the connected instance, moving SQL Server files safely, and checking SQL Server access identities.
