DBAs, developers, and database architects considering using In-Memory OLTP, but not sure if it might benefit their workloads.
You’ve heard that In-Memory OLTP is fast, but how do you know if your workload can take advantage of this awesome feature?
We will explore In-Memory OLTP workload evaluation, use cases, architecture, capacity planning, data migration, hot/cold data, potential impact on disk-based workloads, and more.
By the end of the session, you will have an understanding of how In-Memory OLTP works, and whether your workload is likely to see an increase in performance.
Why I Want to Present This Session:
I’m an In-Memory OLTP evangelist, striving to bring clarity to the misconceptions that I see in forums, blog posts, and in the field in general.
In my quest for expertise, I have read every page of the Microsoft documentation for In-Memory OLTP, verified differences in the behavior between SQL 2014 and SQL 2016, and blogged about many aspects of In-Memory OLTP.