A Fine Slice Of SQL Server
Steve Jones wraps up another T-SQL Tuesday:
Last week I asked you to write about SQL Server 2025 and what things you might be looking forward to in the new version.
Read on for seven entries from some of the more frequent T-SQL Tuesday contributors. Which doesn’t include me, because I am a slacker.
Leave a CommentA quick roundup on some big news from Microsoft Ignite.
John Deardurff hits the marketing materials:
The wait is over! SQL Server 2025 is officially here, and it’s more than just another version. I’ve been working with it during the last six months it was in public preview, and some of the features announced still surprised me. Let’s break down what makes this release so exciting and why it’s a game-changer for businesses and developers alike.
Andy Yun is pleased that Standard Edition just got a lot more powerful:
While all of the new features and such were available during Public Preview, one thing that was not public until now is that Standard Edition limits have been increased! Yay! The CPU core count limit is now 32 cores (or 4 sockets, whichever is lesser) and the max buffer pool memory per instance is now 256GB! Additionally, Resource Governor is now available for Standard Edition. And in SQL Server 2025, Resource Governor can also help you manage TempDB!
Reitse Eskens goes into several useful features, including Express Edition love:
You may have seen earlier blogs from me on SQL Server 2025; I won’t repeat that content in full, but I’ll provide a brief summary. You can find the full blogs here.
Something I wasn’t able to mention before, but you can now find in the documentation, is that SQL Server Express has upgraded its game! No longer a limit of 10 GB for the database, but 50 GB. This makes it much more useful in many scenarios.
Brent Ozar lays out a bunch of features as well:
1 CommentIf you use columnstore indexes, 2025 continues upon every release’s investments, with a bunch of improvements to make management easier on ordered indexes. In my early tests with clients, we’ve seen massive improvements in easier, faster, more online maintenance that we simply couldn’t do before.
I wasn’t really planning on writing a blog post today, but I got curios if there’s anyway in which connections saved in SQL Server Management Studio 21 can be migrated in SSMS 22.
If you’ve installed SQL Server Management Studio 22 you may have noticed that the saved connection details weren’t migrated over from SSMS 21.
It’s documented in the list of known issues for SSMS 22 and marked as having no workaround.
Vlad builds a workaround, probably wearing a lab coat and fiddling with Bunsen burners and beakers full of oddly-colored liquids.
Leave a CommentJohn Deardurff shares the news:
Microsoft has announced that SQL Server Management Studio (SSMS) 22 is now generally available! This latest release brings powerful new capabilities to enhance your SQL Server experience:
Click through to see what’s new and see the original Microsoft blog post on the topic. One thing to note is that the query hint recommendation tool is still in preview, so you do need to select it as an individual component to install.
Leave a CommentChad Callihan is excited about a limitation:
I had written most of this blog post before seeing this month’s T-SQL Tuesday invite. I decided to hold off a few days to post because, while it’s no secret, I think it’s worth pointing out to those that may not know: before you spend time testing SQL Server 2025, make sure you consider what version of Developer Edition to use.
You may read that and ask, “What do you mean? Isn’t there only one Developer Edition?” That used to be the case, but not anymore.
Read on to see why this is important for a large number of companies.
Leave a CommentAndrew Pruski tries out a new feature:
Accelerated database recovery was introduced in SQL Server 2019 and provides fast recovery, instantaneous transaction rollback, and aggressive log truncation. A complete overview of how ADR achieves this is documented here.
Now in SQL Server 2025 we can switch on ADR for tempdb!
Read on to see what benefits you can get.
Leave a CommentAdam Bertram lays out what has changed:
You adopted PowerShell Core 6 early. You moved scripts to .NET Core. You dealt with the compatibility issues. Now Microsoft wants you to upgrade again.
Here’s why it matters: PowerShell Core 6 is no longer supported. Your scripts still run, but you’re missing security patches, performance improvements, and features that make PowerShell 7.5 worth the upgrade.
The good news? Moving from Core 6 to 7.5 is easier than the jump from Windows PowerShell. Most scripts work unchanged. But “most” isn’t “all,” and the differences matter.
Read on to see what will break when moving from PowerShell Core 6 to PowerShell 7.5.
Comments closedSQL Server 2022’s market share has remained pretty stable since its huge jump in Q1, when people replaced a lot of 2016 servers with 2022. With SQL Server 2025’s release approaching quickly, I’m not sure SQL Server 2022 will ever approach the amazing dominant streak that 2019 experienced – that thing’s been a monster! It’s held over 40% market share for two years straight now.
Read on for Brent’s predictions around SQL Server 2025. I tend to agree with Brent’s conclusion around why adoption for 2025—assuming no unforeseen catastrophe in the product—will be more like what we saw with SQL Server 2016 or 2019 versus 2017 or 2022. Which is good, because 2022 and 2025 both have some nice additions to T-SQL that will make database developers’ lives easier.
Comments closedRajendra Gupta tries out a new edition available in SQL Server 2025:
In the article “Install SQL Server 2025 Standard Developer Edition,” we explored the installation of SQL Server 2025 Standard Developer Edition on the Windows platform. SQL Server 2025 (Preview) also works on Linux editions, and it is equally important to cover the installation steps. Let’s see how we can install it on an AWS EC2 instance running Ubuntu.
The first half of the article covers spinning up an EC2 instance. Interestingly, the prompt to choose your edition of SQL Server was only partially updated—it still asks for you to choose an option between 1 and 10, but there are now 11 options available and I’m now curious if the conditional logic in the script to choose your edition works if you want to use Enterprise Core. Rajendra does note an error message that pops up around licensing, but that could be a release candidate thing.
Comments closedRebecca Lewis goes over the list:
Every new SQL Server release comes with shiny features — but SQL Server 2025 brings more than just enhancements. It’s important to know that there are several breaking changes under the hood that could futz your upgrade if you’re not paying attention.
On the whole, it’s a pretty small list but there are a few things on here that could affect any given environment.
Comments closed