Summary

In this chapter, we took a look at the In-Memory OLTP engine as it was introduced in SQL Server 2014. Along the way, we investigated how the In-Memory OLTP differs from the traditional SQL Server storage engine with respect to the concurrency model. The main difference is the ability to allow multiple concurrent users to access the data structure without relying on the pessimistic concurrency model of using locking and latching to uphold data isolation within transactions.

We continued our journey by exploring what T-SQL constructs and data types the In-Memory OLTP engine can support the first version of the feature inside SQL Server 2014. At the same time, we were able to find out that although there are limitations, there is still a wide range of available data types and programming approaches that can be used immediately. Especially exciting is the fact that the T-SQL language receives (almost) transparent support for powerful new capabilities. Memory-optimized tables appear at...