Press "Enter" to skip to content

Category: Versions

Import SSMS 21 Saved Connections into SSMS 22

Vlad Drumea digs in:

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.

Comments closed

SSMS 22 now Generally Available

John 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.

Comments closed

SQL Server Standard Developer Edition

Chad 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.

Comments closed

Migrating from PSCore 6 to PowerShell 7.5

Adam 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 closed

SQL ConstantCare Population Report for Fall 2025

Brent Ozar has an update:

SQL 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 closed

Installing SQL Server 2025 Standard Developer Edition on Linux

Rajendra 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 closed

Breaking Changes in SQL Server 2025

Rebecca 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

TempDB Resource Governor in SQL Server 2025

Brent Ozar tries out an update to resource governor:

We’ve finally got a way to defend ourselves. We can configure Resource Governor to divide people into groups (something that seems to be trendy lately), and then cap how much TempDB space each group can consume. You don’t even have to divide them into groups, either (take note, politicians) – you can just cap how much resources everyone can use altogether.

To keep things simple for the sake of this blog post, let’s just assume we’re limiting everyone’s usage altogether. 

Click through to see how it works, as well as some of the caveats that are going to require foresight before this works the way you’ll want it to.

Comments closed

Migrating from Apache Airflow 2 to 3 on Amazon MWAA

Anurag Srivastava, et al, perform a migration:

Apache Airflow 3.x on Amazon MWAA introduces architectural improvements such as API-based task execution that provides enhanced security and isolation. Other major updates include a redesigned UI for better user experience, scheduler-based backfills for improved performance, and support for Python 3.12. Unlike in-place minor Airflow version upgrades in Amazon MWAA, upgrading to Airflow 3 from Airflow 2 requires careful planning and execution through a migration approach due to fundamental breaking changes.

This migration presents an opportunity to embrace next-generation workflow orchestration capabilities while providing business continuity. However, it’s more than a simple upgrade. Organizations migrating to Airflow 3.x on Amazon MWAA must understand key breaking changes, including the removal of direct metadata database access from workers, deprecation of SubDAGs, changes to default scheduling behavior, and library dependency updates. This post provides best practices and a streamlined approach to successfully navigate this critical migration, providing minimal disruption to your mission-critical data pipelines while maximizing the enhanced capabilities of Airflow 3.

Read on to see what has changed between these two major versions of Airflow, recommendations on what to look out for, and a step-by-step migration guide.

Comments closed