The Next SQL Server Version

Question

The Next SQL Server Version

Steve Jones - SSC Editor

SSC Guru

Points: 736212
More actions
December 31, 2018 at 8:35 pm

#378920

Comments posted to this topic are about the item The Next SQL Server Version

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

George Vobr SSCrazy Eights Points: 9996 More actions · Answer 1

Today's Qotd leads to a secondary question, "What's new in SQL Server 2019?". There are fantastic things there will be enough to study. Thanks for this interesting question, Steve.
Happy New Year to all of you!

Shayn Thomas SSCertifiable Points: 5863 More actions · Answer 2

cheers for the question steve

---------------------------------------------------------------------------------------
The more you know, the more you know that you dont know

Jeff Moden SSC Guru Points: 1004340 More actions · Answer 3

George Vobr - Tuesday, January 1, 2019 5:50 AM
Today's Qotd leads to a secondary question, "What's new in SQL Server 2019?". There are fantastic things there will be enough to study. Thanks for this interesting question, Steve.
Happy New Year to all of you!

A search in Google for the very question you've quoted reveals the answer to that just a few posts from the top of the results.
https://docs.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-ver15?view=sqlallproducts-allversions

While I'm tickled that they've finally realized the concept of how scalar functions should actually work and that they've finally recognized the need for us to be able to handle UTF-8 files, I'm seriously disappointed in what they haven't done for things that have been complaints for a long time.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

George Vobr SSCrazy Eights Points: 9996 More actions · Answer 4

Yes, they did at least something, but I want to start the new year in an optimistic mood ... 🙂

lmalatesta SSChasing Mays Points: 637 More actions · Answer 5

George Vobr - Tuesday, January 1, 2019 5:50 AM
Today's Qotd leads to a secondary question, "What's new in SQL Server 2019?".

I'm most excited about the replacement of the notoriously inconvenient "string or binary data would be truncated" error with something more helpful.

See: https://blogs.msdn.microsoft.com/sql_server_team/string-or-binary-data-would-be-truncated-replacing-the-infamous-error-8152/

And, the best part is it's getting backported to SQL 2016 and 2017!

morlindk SSCrazy Points: 2294 More actions · Answer 6

Oh! … Briefly feared a trick question related to compatibility 'version' rather than 'level'.

Jeff Moden SSC Guru Points: 1004340 More actions · Answer 7

George Vobr - Wednesday, January 2, 2019 7:24 AM
Yes, they did at least something, but I want to start the new year in an optimistic mood ... 🙂

Heh... that would be nice but the engine updates for SQL Server are sorely lacking in that regard.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

George Vobr SSCrazy Eights Points: 9996 More actions · Answer 8

Jeff Moden - Wednesday, January 2, 2019 8:41 AM
George Vobr - Wednesday, January 2, 2019 7:24 AM
Yes, they did at least something, but I want to start the new year in an optimistic mood ... 🙂
Heh... that would be nice but the engine updates for SQL Server are sorely lacking in that regard.

I don't see it so skeptically. Perhaps MS will hear people's voice in other updates... :unsure:

Jeff Moden SSC Guru Points: 1004340 More actions · Answer 9

George Vobr - Wednesday, January 2, 2019 2:38 PM
Jeff Moden - Wednesday, January 2, 2019 8:41 AM
George Vobr - Wednesday, January 2, 2019 7:24 AM
Yes, they did at least something, but I want to start the new year in an optimistic mood ... 🙂
Heh... that would be nice but the engine updates for SQL Server are sorely lacking in that regard.
I don't see it so skeptically. Perhaps MS will hear people's voice in other updates... :unsure:

Considering that they've kept things like the infamous request by Erland Sommarskog for a built in Tally-Table-Like function open for more than a decade but have done nothing about it but did have the time to come up with the rather stupid EOMonth function and considering that they've not added the critical currently missing functionality of String_Split() and have basically ignored all pleas to fix it since before it hit the streets and the fact that they'd release something SUM() OVER() and it took 7 years to respond to pleas to make that work, I'm not getting my hopes up. 😉

Don't get me started on the atrocities committed but never fixed when it comes to the likes of Recursive CTEs and the truly substandard PIVOT operator or the fact they've ignored the fact that Shrink File produces index inversion instead of being done in a Peter Norton fashion, that there's no reason why Index REBUILD should have to temporarily double the size of an index if it's over 8MB (128 extents) or why the supposedly low resource usage REORGANIZE blew out my log file from 20GB to 227B on a 146GB Clustered Index that only had 12% Logical fragmentation. How about the fact that the relatively "new" DATE and DATETIME2 functions still don't have the functionality that the ol' DATETIME datatype has and, instead of fixing it, came out with the (also stupid) DATEDIFF_BIG function to try to make up for it. And how about the wonderful functionality of a BULK_EXPORT and some file handling functions in T-SQL? Yeah.. not happening.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

George Vobr SSCrazy Eights Points: 9996 More actions · Answer 10

Jeff Moden - Wednesday, January 2, 2019 7:44 PM
Considering that they've kept things like the infamous request by Erland Sommarskog for a built in Tally-Table-Like function open for more than a decade but have done nothing about it but did have the time to come up with the rather stupid EOMonth function and considering that they've not added the critical currently missing functionality of String_Split() and have basically ignored all pleas to fix it since before it hit the streets and the fact that they'd release something SUM() OVER() and it took 7 years to respond to pleas to make that work, I'm not getting my hopes up. 😉
Don't get me started on the atrocities committed but never fixed when it comes to the likes of Recursive CTEs and the truly substandard PIVOT operator or the fact they've ignored the fact that Shrink File produces index inversion instead of being done in a Peter Norton fashion, that there's no reason why Index REBUILD should have to temporarily double the size of an index if it's over 8MB (128 extents) or why the supposedly low resource usage REORGANIZE blew out my log file from 20GB to 227B on a 146GB Clustered Index that only had 12% Logical fragmentation. How about the fact that the relatively "new" DATE and DATETIME2 functions still don't have the functionality that the ol' DATETIME datatype has and, instead of fixing it, came out with the (also stupid) DATEDIFF_BIG function to try to make up for it. And how about the wonderful functionality of a BULK_EXPORT and some file handling functions in T-SQL? Yeah.. not happening.

Hmm ... there's something to think about. Thanks for this detailed information, Jeff.

Jeff Moden SSC Guru Points: 1004340 More actions · Answer 11

George Vobr - Thursday, January 3, 2019 7:05 AM
Hmm ... there's something to think about. Thanks for this detailed information, Jeff.

Heh... that's about 1/5th of my total list. 😀 Didn't want anyone to get bored and do a tldr: on it.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)