It is about a few weeks back that I wrote about how InMemory OLTP Hash Collisions can happen and how it can affect performance. Here is a recap of that post for your reference and do check the same before proceeding reading this blog post.
Sometimes the best of learnings are based on people’s questions. I always feel when questions are asked, more the learnings are. In a recent session for a customer who had implemented SQL Server 2014 InMemory OLTP in their systems, they were getting bad performance even when they were using InMemory OLTP.
In one of my recent interaction with my client, they were so much impressed with the fact that SQL Server has now introduced the ability to use In Memory OLTP. They said they were interested in implementing the same in their environment for a number of applications. The hardware refresh was due and they were also upgrading a number of their legacy applications which were hosted on SQL Server 2005 to the latest version as that was also due. In this blog post we will learn about InMemory OLTP Migration Assistant.
InMemory is an awesome concept and I have been fortunate to learn about the same from my friends in the industry over blogs. It holds deep concepts and is sometimes tough to understand how the building blocks come together. I am not the only one doing the exploration, but a number of you also do and pass those learnings to me via your interesting questions. Thanks to each one of you who take a moment to ask me some of these questions that shake the fundamentals and make my understanding stronger. In the same lines, one of the readers wrote back to me after reading the MSDN on InMemory OLTP, what does the concepts of Optimistic multi-version concurrency really mean. On first thought, it looks simple, but the question was very loaded.