If you have a technet account please help vote/bump up sql standard requests

oROEchimaru

Supreme [H]ardness
Joined
Jun 1, 2004
Messages
4,662
To those that agree :)

https://connect.microsoft.com/SQLServer/Feedback/Details/3135172

https://connect.microsoft.com/SQLServer/Feedback/Details/3135989

SQL Standard 2016 is growing archaic and new features in SP1 are unusable due to limitations:
a. maxdop 1 of Index creation (no parallel processing) instead of matching server maxdop or at least maxdop 4 (some parallel processing)... you cannot use compression since the index process alone takes up 100% use of 1 core while 31 cores are idle (or 24)
b. max ram of 128GB in 2017 instead of 256GB or 512GB
c. 24 core limit in 2017 instead of 32
 
I honestly haven't been keeping up with this, but this is significant. Thanks for the heads up. Is there any actual reason being provided for the spec downgrade? Also, anywhere else I can read a tl;Dr change list?
 
Or maybe give up on MS and their batshit crazy licensing and find something else.
 
For enterprise workloads, Oracle licensing isn't any better, especially after the stunt they just pulled for running environments in a cloud that isn't theirs.
 
For enterprise workloads, Oracle licensing isn't any better, especially after the stunt they just pulled for running environments in a cloud that isn't theirs.

Can't argue with that, last Oracle bill hurt. Have IBM coming in again, time to take a lot closer look at DB/2.

Not putting up with this.
 
Back
Top