Ch-Ch-Changes

It's not only the legend that is Mr. David Bowie who sings 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 re-creating the object with the new, updated structure.

For many developers and 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 being able to do without any restriction. With the advent of agile software development and similar development strategies such as continuous integration, being able to make changes to a software application is something many developers look for.

Now it is possible to do just that. We will be continuing this chapter with the same database as in Chapter 11, Introducing SQL Server In-Memory OLTP. We will use the following code to create a simple memory-optimized table, shown as follows...