Oh, Hek(aton)

Nic Cain on Hekaton In-Memory OLTP.  One additional limitation that Nic doesn’t bring up is the lack of foreign key and check constraints.

I’m pretty optimistic about the future of in-memory databases (pun not intended), but this is a V1 product with a lot of limitations.  My initial primary use case would be for staging tables in an ETL environment.  I’d have a very hard time justifying this in a production OLTP environment in which I actually cared about the data.  And given that my job is to be the guy who cares about and protects the data, this might be a tool which doesn’t make it out of the lab for a couple of years.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s