When you first hear about it, SQL Server’s In-Memory OLTP sounds like a new feature that’s hard to implement, requires a lot of schema changes, and takes planning and downtime.
I’m here to tell you it’s simply not true, and you can do it in just 3 steps. Here’s how:
- Read Microsoft’s guidance on how much memory you’ll need
- Give your SQL Server that much
- Set your max server memory setting appropriately, leaving 4GB or 10% free for the OS, whichever is higher
That’s it. That’s all there is.
Forget the feature named “In-Memory OLTP” and just put the hardware in that the feature would require anyway. You’re going to have to do it sooner or later, so just start there. Before you go writing the necessary conflict detection code, trying to rip out your unsupported cross-database queries, messing around with hash index troubleshooting, or stressing out about their statistics problems, just buy the damn RAM.
You’d be stunned at how often that simply makes the performance issues go away.