Ch-Ch-Changes

It's not only the legend himself, Mr. David Bowie, who could sing about changes. In SQL Server 2014, we were destined to create In-Memory OLTP objects that were unchangeable after creation. If we needed to change the structure of a memory-optimized table, we had to resort to dropping and recreating the object with the new, updated structure.

For many developers/customers, this was a deal breaker. Being able to add and remove columns or indexes is something that every SQL Server developer is used to without any such restrictions. Especially, with the advent of agile software development and similar development strategies such as continuous integration, making changes to software applications is something many developers strive towards.

Now, with SQL Server 2016, it is possible to do just that. We will be continuing this chapter using the same database as in Chapter 11, Introducing SQL Server In-Memory OLTP, creating a simple memory-optimized table:

USE master 
GO 
CREATE...