No plans, but I have advised two clients to consider replacing SQL 2012 with SQL 2014 in their upgrade plans. Partially because, knowing these guys, they won't actually upgrade until around 2016, but also so that I can consider Hekaton for very specific, very carefully targeted portions of their systems.

Not that they're in any way at the point that there are no other performance gains to be had. Hell, most databases I see it's a combo of 'Did a cat throw up on that stored proc, or did you write it that way?', 'Indexes? What are they?' and '2003 called and would like its hardware back' :hehe: