Hekaton was a new way of storing data in SQL Server 2014. In-Memory OLTP can actually be really cool. Here are some of its advantages:

  • It stores data differently in a way that eliminates latch waits
  • If your stored procedures use a subset of T-SQL commands, they can get compiled to native code and run much faster
  • If you don’t need to persist the data to disk, you can skip disk writes altogether and just have some RAM-only tables

But you need to understand the limitations, and they’ve changed a lot over the years. Click on the links to learn more about each restriction:

Whew! That’s a lot of limitations – make sure you understand those fully, because it impacts how you manage a database with Hekaton tables. Things got better in 2016, though.

To Learn More About Hekaton

List out the Hekaton tables to identify:

  • Their table sizes (keeping in mind their projected growth, your version’s memory limit, and the double-memory requirement)
  • Their data storage (they may not be persisted to disk, so you’ll have an ugly surprise when rebooting the server)

Watch Brent’s DBA Reactions Guide to Hekaton

Menu
{"cart_token":"","hash":"","cart_data":""}