A memory-optimized table variable with a NONCLUSTERED index consumes way too much memory - by NedOtter

Status : 


Sign in
to vote
ID 2847169 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 6/22/2016 5:44:04 PM
Access Restriction Public


If you need to migrate data from a source database to an in-memory table in a different target database, one of the options is to use a memory-optimized table variable, based on a table type Depending on how you define the index for the table type, memory consumption is orders-of-magnitude higher, so much so that even with sufficient memory on the server and a resource group created at 90% min/max, the resource pool runs out of memory. 
Sign in to post a comment.