One of the most important differentiators amongst SQL Server 2014 and its earlier counterparts is in the former’s support for in-memory database tables. When our computer systems go slow we ...

In SQL Server 2014 there were a number of restrictions on memory-optimized tables: you couldn't alter their structure after they were created; many SQL operators weren't supported (Outer Joins, ...

This whitepaper illustrates the SQL Server 2016 business intelligence/data warehouse upgrades, the memory-optimized tables, and the columnstore indexes. We also discuss the performance comparison of ...

Memory Optimized Tables promise significant performance gains, but tend to be difficult to work with. SQL Server 2016 reduces much of the pain by offering ALTER TABLE support.

In SQL Server 2014, Microsoft is introducing the In-Memory OLTP database engine which essentially performs the entire I/O operation set against selected tables straight from memory.

The CTP2 release of SQL Server 2014 is a test release or "evaluation edition" that will expire on March 31, 2014 and can be downloaded here. However, Clark described it in his announcement as "our ...

Along with Linux support, SQL Server 2016 includes improvements to its “Hekaton” in-memory database engine introduced in the 2014 version. Microsoft said in its release notes that the storage format ...

As with memory-optimized tables, compiled procs were introduced in SQL Server 2014 with some restrictions, many of which were removed in SQL Server 2016. For example, in SQL Server 2016 compiled ...