Hekaton: SQL server's memory-optimized OLTP engine

By C. Diaconu, Craig S. Freedman, Erik Ismert, P. Larson, Pravin Mittal, Ryan Stonecipher, Nitin Verma, M. Zwilling. ACM SIGMOD Conference, 2013

538 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Persistent B+-Trees in Non-Volatile Main Memory (2015, methodology): “Examples include the IBM Blink project [3], the Hekaton OLTP engine in Microsoft SQL Server [10], and SAP HANA [24].”
EnclaveDB: A Secure Database Using SGX (2018, unknown): “Hekaton [16] is a database engine in SQL Server optimized for OLTP workloads where data fits in memory.”
In-Memory Big Data Management and Processing: A Survey (2015, methodology): “Examples of commercial in-memory relational databases include SAP HANA [77], VoltDB [150], Oracle TimesTen [38], SolidDB [40], IBM DB2 with BLU Acceleration [223], [224], Microsoft Hekaton [37], NuoDB [43], eXtremeDB [225], Pivotal SQLFire [226], and MemSQL [42].”
Speedy transactions in multicore in-memory databases (2013, background): “The Bw-tree [21] is a high-throughput multiversion tree structure optimized for multicore flash storage.”
No compromises: distributed transactions with consistency, availability, and performance (2015, background): “In Proceedings of the 30th International Conference on Very Large Data Bases (2004), VLDB’04.”