When the In-Memory OLTP engine was introduced in SQL Server 2014, Microsoft announced that the maximum size of any memory-optimized table was 256 GB. This limit was reached using internal testing at Microsoft and was introduced to ensure the stability and reliability of the feature in production environments. The main decision here involved the design of the storage subsystem, particularly around the checkpoint file pairs. There was a hard limit of 8,192 checkpoint file pairs, each capable of storing 128 MB of data, however the limit of 256 GB was not a hard limit, and was rather a suggested maximum.
The memory requirements for a memory-optimized table are dynamic. This dynamism is grounded in the memory requirements for ...
