[Forthcoming] Doing it wrong - Hekaton.

Okay, I've got an idea for a series of blog posts.  I've recently implemented In-Memory OLTP (IMOLTP, which I will now start pronouncing Im-Ho-Tep), and learned a bunch in a short period of time.  Don't do it like me.  Do it better.

Many thanks to Ned Otter for helping out a ton during this time.

Create in-memory FG

Create in-memory table

Create second in-memory FG

Create/destroy to new name
Stored procedure not working - still needs to only be in THAT database. No cross-DB work in SPs!

Resource issues!  (show event log)

Missing inserts copying from _live to _main? Why? (all about the COMMITs)

Answer: flip the order we get the IDs.

Pare down for now so we don’t run out of memory

DBCC caused problems with memory

Identity value on both table – have to monitor

Resource governor to the rescue?

 (I did this part, but remember to take the DB offline/online and sweat while it takes forever to come up)

Rebalance the In-memory filegroups if you have older data in there!