InMemory OLTP
10 TopicsWhat to do when you run out of disk space for In-Memory OLTP checkpoint files
First published on MSDN on Dec 23, 2015 While data for memory optimized tables resides in memory all the time with SQL Server 2014 and 2016's In-Memory OLTP feature, we still need a means to cut down recovery time in case of crash or restart.5.1KViews1like0CommentsUnable to issue alter table for a memory optimized tables
First published on MSDN on May 10, 2017 Recently I assisted on a customer issue where customer wasn’t able to alter a memory optimized table with the following error Msg 41317, Level 16, State 3, Procedure ddl, Line 4 [Batch Start Line 35]A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases model and msdb, and it cannot write to master.914Views0likes0CommentsBe aware of 701 error if you use memory optimized table variable in a loop
First published on MSDN on Feb 22, 2017 In blog “Importance of choosing correct bucket count of hash indexes on a memory optimized table”, I talked about encountering performance issues with incorrect sized bucket count.1.1KViews0likes0CommentsSolve your tempdb problems with memory optimized tables
First published on MSDN on Mar 25, 2016 if you are on SQL Server 2014 and above and have tempdb problems, SQL Server In-Memory OLTP Program Manager Jos de Bruijn just posted a great blog titled “Improving temp table and table variable performance using memory optimization”.728Views0likes0Comments