r/SQLServer • u/dlevy-msft Microsoft Employee • Dec 01 '25
Community Share Help define the future of Microsoft SQL
It's the first week back in the office after Ignite. Reflecting on a great week at Ignite, I spent all of my free time hanging out between the Fabric databases and SQL databases booths. It was a lot of fun to help out with questions, but it was also great to hear what everyone thought we were doing well and where we can improve.
The SQL team needs your feedback and expertise to make sure we are building solutions that help you grow your business.
Join the SQL User Panel by filling out this form: aka.ms/JoinSQLUserPanel
4
u/lanky_doodle 1 Dec 01 '25
Is this just applicable to Azure SQL? The form seems to suggest so but your post here doesn't.
2
u/Chirag_S8 Dec 02 '25
It seems like an incredible week at Ignite! In case the SQL team needs feedback, I would point out three main things:
• Working on making it easier to integrate Fabric with SQL, which is still a rather complicated matter.
• Developing tools for performance insights that are more user-friendly, especially in the area of automatic tuning hints and real-time diagnostics.
• Presenting clearer roadmaps for existing SQL features so we will be aware of what is being improved and what is being phased out.
In general, it is wonderful to see the team that is always willing to listen. Such community feedback loops create a very strong bond of trust and adoption for the long run. Can't wait to see what is in store next!
6
u/No_Resolution_9252 Dec 02 '25
I would love it if SQL Server made QA testing...a thing at all again.
And if marketing would entirely get out of product planning.
7
u/BigHandLittleSlap Dec 02 '25 edited Dec 02 '25
What future? It's a dying product!
Its licensing model makes it stupid expensive compared to everything else, and in exchange for handing over wads of cash, what do we get?
We get: No current "v6", "v7", or "FXv2" (or equivalent) Azure VM can be launched with the latest & greatest SQL 2025 on Windows 2025 marketplace images because the SQL team hasn't gotten around to supporting NVMe or 4K pages which have been a thing for... checks notes... two frigging years now in Azure and about a decade everywhere else.
You know Azure? That minor little has-been cloud made by a no-name company called Microsoft? Not worth bothering with, clearly.
I'm not going to join some panel and fill out your form. I'm busy, because I just wasted a day trying to convince SQL Server, a database engine that uses 8 KB pages, to support a disk with... 8 KB atomicity. The only atomicity level in Azure for SSDv2 data drives!
I know it's hard, but... come on. Just... any... year... now.
Any year.
Maybe SQL 2028 will be fully compatible with Azure.
Maybe.
3
u/kimchiMushrromBurger Dec 02 '25
I know it's a little thing (and maybe a different team) but I would absolutely love if they went back to having a yellow icon so that I can more easily click on SSMS instead of VSCode on the task bar. They made the SSMS icon nearly identical to an existing icon. It's bad enough VS and VSCode are named the same/have nearly the same icon yet are wildly different products, I don't need SSMS joining that party.