Announcing SQL Server 2025

Question

Announcing SQL Server 2025

Press Release

SSCarpal Tunnel

Points: 4393
More actions
November 22, 2024 at 12:00 am

#4486576

Comments posted to this topic are about the item Announcing SQL Server 2025
March 18, 2025 at 10:52 pm

This was removed by the editor as SPAM

Viewing 10 posts - 1 through 9 (of 9 total)

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

Dan Sutton Newbie Points: 2 More actions · Answer 1

Does it support .Net 5+ in CLR? It's kind of annoying having to restrict myself to .Net 4.8 for large projects sharing code with CLR backend stuff...

Steve Jones - SSC Editor SSC Guru Points: 737930 More actions · Answer 2

No idea. Details are few and far between, but I'd think they'd rev the .NET support

Dan Sutton Newbie Points: 2 More actions · Answer 3

Yeah. Back when it was SQL Server 2019, they posted this, which sucks.

https://www.microsoft.com/en-us/sql-server/blog/2021/09/08/open-sourcing-the-net-5-c-language-extension-for-sql-server/

I'm hoping this isn't their ultimate solution. I know .Net 5+ (so-called "Core") is an entirely different set of DLLs, i.e. a discrete language environment which has nothing to do with the "original" versions... I kind of think they've forgotten about CLR and are hyping Azure instead.

Jeff Moden SSC Guru Points: 1004591 More actions · Answer 4

I just want them to fix the serious performance problems that started in 2019 and they've done (apparently) nothing to fix even up 'til today for SQL Server 2022. 🙁

--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)

Ken McKelvey SSCoach Points: 18895 More actions · Answer 5

Jeff Moden wrote:

I just want them to fix the serious performance problems that started in 2019 and they've done (apparently) nothing to fix even up 'til today for SQL Server 2022. 🙁

I would not hold you breath as:

most of the development work seems to be focused on Azure.
having to buy 20% to 30% more core licences generates more revenue for Microsoft. They have probably correctly calculated that this is not enough of an annoyance for most people to seriously start looking at something like PostgreSQL.

Ken McKelvey SSCoach Points: 18895 More actions · Answer 6

An interesting article:

What the Decline of Sql Server Quality means for Developers and DBAs

ratbak Default port Points: 1407 More actions · Answer 7

"this is not enough of an annoyance for most people to seriously start looking at something like PostgreSQL"

Most? Probably still true. But they might want to re-evaluate their over-confidence and disdain for users.

Postgres growth numbers are incredible.
We're seeing more and more well-known MSSQL leaders embracing postgres.
Open source growth in general, and movement to the cloud, are are increasingly pulling businesses away from the Microsoft stack.

Ken McKelvey SSCoach Points: 18895 More actions · Answer 8

ratbak wrote:

"this is not enough of an annoyance for most people to seriously start looking at something like PostgreSQL"
Most? Probably still true. But they might want to re-evaluate their over-confidence and disdain for users.
Postgres growth numbers are incredible.
We're seeing more and more well-known MSSQL leaders embracing postgres.
Open source growth in general, and movement to the cloud, are are increasingly pulling businesses away from the Microsoft stack.

Some good points but maybe Microsoft are being visionary. I find what they are attempting to do with Fabric to be a bit mind blowing and do not really understand it. The idea of automatically replicating SQL data into OneLake certainly piques my interest.

At the moment I suspect the best SQL database for large numbers of users with high transaction rates is still Oracle but you really, really pay for the privilege. I think SQL Server is still the best mid-range option with plenty of support. Moving to Postgres has a learning curve and if just considering SQL might be a good option. It could be better to look at something like Fabric which may be easier to integrate into AI etc. No doubt time will tell.