News & Opinion

Upcoming SQL Server 2019 Features

If you think that's big, you should see the size of the drink
If you think that’s big, you should see the size of the drink

I happened to be in Seattle this week after finishing up an Alaska cruise, and I had the chance to sit down with some of the PMs responsible for upcoming SQL Server features. It turns out they’re already deep in development with some truly revolutionary capabilities.

Now, I probably shouldn’t be sharing these with you, dear reader, but I bet you’re going to be as excited as I am, so here goes: SQL Server 2019’s upcoming feature list:

  • Edible Result Sets
  • Self destructing transactions
  • New SSMS color schemes by Karl Lagerfeld
  • Deep South Parent/Child Referential Integrity (I didn’t wanna ask for details there)
  • Eventual consistency
  • Scented error messages
  • Duraflame Transaction Log
  • Access storage engine
  • MAIM command – like KILL, but lets you keep up to half of the result sets that have already been delivered
  • Renaming SQL Server Agent to Cortana
  • Twitch integration for video replay of cool transactions
  • Azure Power Enterprise Server – I’m not quite sure what this is because the description changed three times while we were talking, and the name changed four
  • Opinion-based triggers
  • TSA-grade security

Erik says: I’m kinda excited about the new upcoming family valued functions, emoji support, and Haskell functions. The best, though, has to be IntentiSense, which replaces IntelliSense, and detects what you meant to write.

Free, 3× a week

Get my new posts by email

Three posts a week, plus a Monday roundup of the best database news from around the web.

72 comments

  1. I hope IntentiSense will fix one of the most vexing problems of the SQL language: the lack of the FORM keyword. As in:

    SELECT * FORM table

    which should be a legal statement. I’ve had to get two backspace keys replace because of this limitation.

    Either that, or FORM should be added to ANSI SQL.

  2. Opinion based triggers, Eventual consistency, self destructing transactions and duraflame transaction log sound really interesting.

      1. What MS is doing is bring features that’s in MongoDB and other NoSQL databases to their RDBMS product. I’ll stay clear from MongoDB 🙂

  3. Looks at calendar…
    Looks at post again…
    Scratches head…
    “But, April Fools isn’t for another 8 months?”

    1. To the BrentO Family,
      The origins of my comments are from a place of love.
      Early-On you’ve encouraged me to reach beyond to understand the nuances of SQL Server and I’m forever grateful for that. However, you’re brand is becoming increasingly diluted and irrelevant more recently. This post is an example of what I’m referring to. Many people will laugh this off, however, its a prime example of the distorted Zaniness the brand has evolved into. I’ve also watched a number of more recent “Office Hours” and I’m sad to see that its a bunch of “condescending question deflection” mostly from an irritated New Yorker living in a closet. Pls Help.

      1. BrentORules – thanks for taking the time to write that. I appreciate that it’s not always easy to write what you’re thinking, and I know you’re trying to help.

        Thing is, we’ve always been about distorted zaniness.
        Dressing up as Richard Simmons to teach you about wait stats: https://www.brentozar.com/sql-server-training-videos/wait-stats-lose-wait-fast/
        Using Lady Gaga to explain SQL Server 2008 R2: https://www.brentozar.com/archive/2010/05/sql-server-r-review/
        Using race car drivers to teach you performance tuning: http://sqlbits.com/Sessions/Event5/T-SQL_Tuning_with_Colin_Chapman_Enzo_Ferrari_and_The_Stig

        I could go on and on, but zaniness has been a core part of my brand since I started writing online well over a decade ago. It sounds like we’re not really the blog for you. I totally don’t take offense, but we’re not going to be getting any more serious anytime soon. Thanks for taking the time to write, though.

  4. I heard that they were going to deprecate Full-Text and replace it with Bing. Maybe in 2020.

  5. scented error messages! Finally! Now Microsoft just needs to work with manufacturers to develop scratch-and-sniff monitors.

  6. Brent,

    I think you missed where they are going to replace linked servers with LinkedIn servers….

    I could not resist….

  7. I’ve always wanted to know what result sets taste like, and even more, does the taste differ between sets? Can I taste-code a query window, sort of like I can color-code one today? Gosh, I’m excited!!!

  8. All topics sounds interesting and would be eager to learn following

    IntentiSense
    Self destructing transactions
    MAIM
    Renaming SQL Server Agent to Cortana
    Twitch integration for video replay of cool transactions
    Duraflame Transaction Log
    Access storage engine

    Thanks

  9. I think Brent is still recovering from the drink he put that ice cube into. 🙂

    This post made my day. I do wish that intentisense were real, because I also tend to type FORM instead of FROM….

  10. Long-lasting LOLs here… and Brent, maybe it will have Fingerless Search & Replace for your gloves (who holds ice with those ??!! ) !

  11. I like self-destructive transactions, can they be smart enough to not even start ? Or is it a feature for SQL 2020? 🙂

  12. Yay! They’re going to bring back Hot Dog Stand color scheme, right?!?!
    I would also up-vote ‘FORM’ as a legal synonym for ‘FROM’, and Intentisense. I’m pretty sure my developers have already coded self-destructing transactions.

  13. Why not also do something about the word database as well. Did anyone ever notice it is typed fully by the fingers of your left hand? Very inconvenient.

    As for features, I’m all for introducing the concept of mood dependent query options using the WHEN clause, e.g.:

    SELECT * FROM TASKS
    WHEN Weather = ‘Good’

  14. “TSA-grade security” would be a downgrade from the integrated AD security with your packets being lost is transition. When they are finally were found in the wrong client, they would include the label “Inspected for your safety by the TSA”

  15. “Renaming SQL Server Agent to Cortana” – only if the error messages come with a voice message. Just Jen Taylor’s voice saying “Chief, we’ve got a problem. Looks like a job failed. Chatter on the Covenant battle net indicates a divide by zero error occurred. Interesting…we’d better go take a look.”

  16. Why are they adding all those features? I just want SQL 18 to support the SQL-98 standard “LIKE YOU KNOW” wildcard search.

  17. Hope MS improve their error messages before implementing the scented error messages… There is a few crappy errors, I can only imagine what they are gonna smell like!!

  18. What would be really cool would be writing TSQL in ones own native language. now wouldn’t that be cool.
    LanguiSense ?

  19. Edible Result Sets! Will there be a menu of choices? Gluten-free option? Vegetarian? This is going to make it easy when you’re coding for hours and starving!

    1. Maybe, but only if they give you a reason to. They will, however, be required to take off their shoes and go through the body scanner, so you’ll have THAT mental image to deal with. Oh yeah, they’ll need to query their data up to 2 hours before they want I to allow for screening.

  20. Hahahahah when i started reading your articule, i said “OMG is this true?”, until the emoji support
    (?? ???)?????

    You made my day!!!

    thanks, men! ( ?~ ?? ?°)

  21. Very good Brent! I also heard about this potential feature:

    TINDEX – finds rows with the “best looking” data for your queries.

    Cheers
    Terry

  22. @Terry Catt – I thought T’INDEX would have been for the SQL Server 2018 Yorkshire Edition – which also comes with the obligatory TooBloodyExpensiveAsNutPayingFerThat Enterprise Input Commands. (Sorry US posters who may not understand this!)

  23. Can’t believe no one remarked on your jacket – with ORACLE written on your chest!! TRAITOR!! 😀

    1. Kevin,
      Lets not start rumors that Brent goes both ways – ORACLE and SQL. He is just well rounded.
      Many of us go “Old School” with DB 2 on main frame and are not judged for that.
      The only scary thing is “Eventual Consistency” is a reality in sharded databases – that is not a rumor but fact.
      https://en.wikipedia.org/wiki/Eventual_consistency

  24. Scented error messages would bring a whole new meaning to SQL Server code smells. I thought we already had self destructing transactions, since I’ve had to help our developers troubleshoot zombies in there C# code, and I thought the Access storage engine is LocalDB? 😉

  25. TSA-grade security – Touching, Squeezing, Aggregating ? Oh wait that was security not selects
    This was truly funny. No House of Duras Klingon joke? Like their new battery that captures and holds electricity? Yea, Wal*Mart sells them as Duras – cells 🙂 LoL
    Who says DBAs do not have a sense of humor

  26. Hi Brent,

    Thanks for the great info. This is truly big news, seriously.

    Apart from that, can you shed light as to whether database replication will be supported for tables with Clustered Columnstore Indexes (CCI)? I have now faced a replication scenario for an existing database with CCI. Seems like there is currently no version of SQL Server that natively supports both Transactional Publications and CCI. This is a huge frustration for me and I hope the team will come up with a solution in 2018. Please cheer me up!

Leave a comment

Your email address will not be published. Required fields are marked *

Email me about new comments: