Managing Memory for In-Memory OLTP
Applies To: SQL Server 2016
Memory-optimized tables require that sufficient memory exist to keep all of the rows and indexes in memory. Because memory is a finite resource, it is important that you understand and manage memory usage on your system. The topics in this section cover common memory use and management scenarios.
In this section
Section | Description |
---|---|
Estimate Memory Requirements for Memory-Optimized Tables | Estimate a table’s memory needs. |
Bind a Database with Memory-Optimized Tables to a Resource Pool | Step by step walkthrough to bind a database with a resource pool. |
Monitor and Troubleshoot Memory Usage | Tools you can use to monitor your memory usage. Also covers troubleshooting if memory usage gets too high. |
Resolve Out Of Memory Issues | Steps to recover from an OOM (Out of Memory) situation. |
Restore a Database and Bind it to a Resource Pool | Steps to restore an In-Memory OLTP database and bind it to a named resource pool. |
In-Memory OLTP Garbage Collection | Understand how garbage collection operates on deleted rows. |