>Bummer... Just like materialized and indexed views are only available in the enterprise version. That is just not an option for us. I see you're still a fan of stored procs. What is the relation between Hekaton and stored procs?


Yes, the new in-memory OLTP engine is only for the Enterprise edition, and only for the 64-bit version. I know many who use the BI edition of SQL Server are understandably frustrated, but I can at least see the requirement for 64-bit.

Yes, still a fan of stored procs. I think every client I've had since 2004 has used them extensively.

On stored procs and Hekaton, there's good news and bad news.

The good news is that stored procs that read from/write to Hekaton tables can be designated for native compilation. Between that and the general benefits of Hekaton to begin with, some installations are seeing at least a 5x boost in performance. In that sense, it's not unlike the columnstore index in SQL Server - not every context can benefit from it, but when you can, the boost is huge

Now for the bad news. Many data types are unsupported and certain functions aren't supported.

My perspective, where I see Hekaton being broadly helpful, is in staging tables. I'm working with one company on some benchmarks and we're seeing speed gains of over 4x.