CelebratingToday, April 1st, 2014, marks the release of SQL Server 2014. There are tons and tons of great new methods and functions and processes within the product. We’re all going to be learning about them for quite a while to come. One of the most exciting though is one of the changes to the defaults. In the past there’s been a lot of debate around how best to configure your databases. What cost threshold should be set for parallelism, the max degree of parallelism, memory settings, auto growth, and all sorts of other settings affect how your databases work. But, Microsoft has finally done something smart. They’ve bowed to the pressure of hundreds and hundreds of DBAs, Database Developers and Developers around the world. They’ve finally done the one thing that will improve everyone’s code once and for all. Expect to see massive performance improvements in SQL Server 2014 thanks to this one default change.

What have they done you ask? What miracle is this that is going to result in both better code and better performance? Simple, by default, all connections to the database are now using the transaction isolation level of READ_UNCOMMITTED. In a single stroke, we no longer are forced to put with WITH NOLOCK on every single table reference in every single query. All the pain and suffering caused by blocks from locking has been removed from the product. We can look forward to a much cleaner code base and better query performance. Thanks Microsoft.

Please, note the date carefully.

15 thoughts on “SQL Server 2014 New Defaults

  1. It’s too early in the morning for this! I had to read it three times to realize you weren’t saying read-committed snapshot isolation!

    Grant Fritchey, the Cruel DBA, got me first this year.

  2. Although I caught it the first time, I agree with Steve. Since I was thinking about the date already, I figured there was something wrong because in there somewhere. Good one!

  3. Ok, Grant… you owe me a new monitor, keyboard, and some fresh underpants. I blew coffee out of every facial orfice laughing and farted really hard after I read this. “It Depends” suddenly has a whole new meaning for this ol’ man. Too funny! 😉

    The odd part is that you actually might not be that far off especially where Hekaton is concerned. It’ll be interesting to see how many people lose or overwrite data by mistake with the rather optimistic locking done there.

  4. Revolutionary!!!
    Can you explain the Blow to the Head tag?
    I am having a hard time relating that to the article…..
    I thought I felt an aftershock from California, but I can see maybe it was actually centered to my East.

  5. Thanks for all the feedback.

    Greg, the “blow to the head” tag means that if I really thought that changing the default behavior of the databases to allow for dirty reads was a good idea, it was because I had taken a blow to the head.

  6. And I was thinking ‘what a novel feature, why didn’t they do this years ago’ ;>)

    Thanks for the good humor to set the starting point for the day!

  7. although I’ve just read this on the 4th, I still thought it must have been a joke. But a very good one! Nice!

  8. Pingback: weight loss plans

Leave a Reply