Summary
In this chapter, we covered how the In-Memory OLTP Engine has evolved from the first version released with SQL Server 2014 to the latest version in SQL Server 2016.
Many of the restrictions around data types, constraints, large binary objects, and collations, along with the ability to alter objects without having to drop and recreate them, provide us all with huge improvements for developers. However, we have also seen that there are still limitations and areas where the use of In-Memory OLTP is not the best choice, or must at least be carefully considered before being chosen for a particular implementation.
A vastly more efficient processing engine allows us to consider scenarios where current implementations may benefit from the reduced ...
Get SQL Server 2016 Developer's Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
