The limits for Columnstore segment cache is per SQL Server instance across all the databases in the instance. If you would like to estimate memory size required for your data, please refer to Estimate Memory Requirements for Memory-Optimized Tables. The limits for In-Memory OLTP data is per database.

On all lower editions of SQL Server 2016 starting with SP1, we have memory quota limits for In-Memory OLTP data and Columnstore segment cache which is in addition to the maximum buffer pool memory limits described earlier. This is not specific to SQL Server 2016 SP1 and is also applicable to earlier releases of SQL Server as well.Įssentially, SQL Server in lower editions can consume and utilize memory outside the maximum buffer pool memory limit defined in the table above due to memory consumed by other caches. The memory consumed by caches outside buffer pool is not restricted by above memory limits and can grow up to limits defined by 'max server memory'. The rest of the caches in the SQL Server memory (procedure cache, thread stack, backup buffers etc) consumes memory outside buffer pool memory. In simpler terms, buffer pool memory in SQL Server is a memory cache responsible for caching data and index pages for the entire instance. The memory limit defined for lower editions of SQL Server is essentially Maximum buffer pool memory limit. In the past, the memory limits defined in table above in the SQL Server editions page for lower editions were referred to as Maximum memory utilized per instance which did not accurately reflect the true limits.

Understanding the Memory limits for lower editions of SQL Server Memory: Maximum memory utilized per instance buffer pool size per instance

Download ms sql server 2016 express