June 21, 2016 at 2:54 am
Hi,
I am thinking about using memory optimization, but my biggest worry is the system running out of memory. The part of the data that would be memory optimized would not exceed the size of my RAM, but I know that I have other tables that would - would the engine always keep a reservation for the memory optimized tables, so that they would not be affected by high RAM usage in other areas?
The only thing that I can have been able to find about reserving memory is making a resource pool, but this maps to an entire database. The entire database does contain large tables larger than all my RAM, so I am worried that the memory optimized tables would fail to work, if SQL server does not prioritise RAM requests from the mem optimised tables, within the database. I can't separate out the memory optimized data into its own database, as memory optimised data can only work within its database, so I can't use a resource pool just for the memory optimised data, as this data joins onto normal data.
Has anyone had any experience with this that they could share?
June 21, 2016 at 5:13 am
The memory-optimised tables are memory-resident, they cannot not be in memory. What memory is left over from that is the normal SQL buffer pool and managed as normal for the buffer pool. If the memory-optimised tables grow, the buffer pool shrinks.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply