When In-Memory OLTP came out, I worked with it briefly, and I remember coming away thinking, "Who in their right mind would actually use this?" I was so horrified that I wrote a presentation about it and gave it at a couple of conferences:
https://www.youtube.com/watch?v=Nlrc56Q4ABQ
When In-Memory OLTP first came out, Microsoft liked to go around bragging at conferences that "Nothing stops a Hekaton transaction." I remember hearing that and kinda chuckling at the time, and I was reminded of it by a recent client who was running into blocking issues with...yep, Hekaton.
To reproduce it:
A really odd choice
I've talked a bit about my annoyance with hardware limits for Standard Edition here and here.
If you're a bunch of SQL-savvy developers who understand the Enterprise Edition features that are now available in 2016 SP1, great. You're a very small minority of shops. I'm talking about places like StackOverflow and kCura.
Starting with today's release of SQL Server 2016 Service Pack 1, Standard Edition now has a lot more of the features of Enterprise Edition. Here's the list from Microsoft's announcement post:
Performance features - in-memory OLTP (Hekaton), in-memory columnstore, operational analytics
Data warehousing features - partitioning, compression, CDC, database snapshots
Some security features - Always Encrypted, row-level security, and dynamic data masking
With the release date for 2016 finally announced Everyone can start gearing up to gaze upon its far shores from the 2008R2 instance they can't or won't upgrade for various reasons. I'm excited for a lot of the improvements and enhancements coming along, and generally hope I'm wrong about customer adoption. One annoyance with the…
tl;dr - run a copy-only full backup of the Hekaton filegroup to nul. If the backup fails, you have corruption, and you need to immediately make plans to either export all your data, or do a restore from your last good full backup, plus all your transaction log backups since. Yeah, that one's gonna need a…
At SQLbits last month, I presented a new session: Cool Story, Bro - The DBAreactions Guide to SQL Server 2014. I wanted to have some fun while educating folks about the surprise gotchas of the newest features.
Here's the In-Memory OLTP (Hekaton) section of the session:
The latest version of our free SQL Server health check adds some nifty new stuff: Checks for non-default database configurations like enabling forced parameterization or delayed durability Looks in the default trace for long file growths or serious errors like memory dumps Checks Hekaton memory use and transaction errors Warns about database files on network…
There's a couple of new features in SQL Server 2014 that provide options for how you work with temporary objects. Will inline index creation or memory optimized temporary tables forever change the way you code? Let's take a look! Inline Index Creation SQL Server 2014 brings us a TSQL improvement called "inline specification of CLUSTERED…
This morning at the PASS Summit, we have the pleasure of listening to Professor David DeWitt talk about Hekaton internals.
I'm actually not going to liveblog this - I'm going to sit back and take in the presentation as an attendee because it's going to be so damn good, and I'm not going to be able to do justice to it in a live blog post. I need to explain why.
