Press "Enter" to skip to content

Category: Versions

REST API Invocation in SQL Server 2025

Tomaz Kastrun continues an advent of SQL Server 2025. First up is external REST API endpoint execution:

This new functionality, you can call to the system stored procedure sp_invoke_external_rest_endpoint, and call / get:

– Call REST/GraphQL endpoints from other Azure services
– Have data processed via an Azure Function
– Update a Power BI dashboard
– Call an on-premises REST endpoint
– Talk to Azure OpenAI services

Then, Tomaz uses this to call a language model:

After short introduction into the  sp_invoke_external_rest_endpoint we will look into creating a REST endpoint for using LLM.

Leave a Comment

Backups on Secondary Replicas in SQL Server 2025

Brendan McCaffrey takes a look:

Back in 2022, I wrote a post called SQL Server Backups on Secondary Replicas: Best Practice or Bad Idea? At the time, the limitations were clear: backups on secondaries were restricted, operationally risky, and often misunderstood.

Three years later, SQL Server 2025 has expanded what you can do on a secondary replica. Some of these changes are genuinely great. But the question I keep getting is:

Does SQL Server 2025 finally make backups on secondary replicas a best practice?

Read on for the answer.

Leave a Comment

Upgrading to SQL Server 2025

John Deardurff checks out a tool built into SSMS 22:

Starting with SQL Server Management Studio (SSMS) 22, the Hybrid & Migration Component delivers a streamlined experience for upgrade assessment and side-by-side migration. This replaces the Data Migration Assistant (DMA) that retired on July 16, 2025, consolidating assessment and migration into one tool. So what are the key capabilities:

Click through for those capabilities and a few tips on how to use it. I’m not sure how clean the upgrade process is to 2025 versus standalone installation. I’d imagine that, if you’re not using something like ML Services, it’s probably fine.

Leave a Comment

Thoughts on CPU Optimization and SQL Server Licensing

Brendan McCaffrey cuts some cores:

Minimizing CPU core counts is a perfect example of how to add value, and is arguably one of the easiest ways to do so.

I run this exercise in my environments about every six months, typically right before true-up time and again at mid-year, just to make sure we haven’t drifted too far.

Read on to see what Brendan does.

This next bit is weird for me to write because I’ve always been an Enterprise Edition snob. But another tip that I have is to take a very serious look at Standard Edition. If you’re using SQL Server 2025, you can have up to 32 cores and 256 GB of RAM in your buffer pool. Taking a look at the available features, losing online index (re)builds and superior availability groups sucks, but it’s not the end of the world for most shops. If you have large enough databases to really benefit from online index rebuilds, read-ahead scans, merry-go-round scans, batch mode on rowstore, and the like—generally, data warehouses or large OLTP instances with heavy read workloads—then those could benefit from Enterprise. But the cost in terms of lost functionality has decreased considerably in the past decade.

Leave a Comment

SQL Server 2025 Now GA

A 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:

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

1 Comment

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