Press "Enter" to skip to content

Category: Versions

Creating a SQL Server 2025 Practice Environment

Published 2025-12-31 by Kevin Feasel

John Deardurff installs SQL Server 2025:

Microsoft SQL Server 2025 introduces major advancements in performance, security, and built‑in AI capabilities. Before you can start exploring its new features, you need to install it correctly. This guide walks you through the full installation process of SQL Server 2025, SQL Server Management Studio 22, and restoring the AdventureWorks2025 database to create a practice environment to test the new features and enhancements of this new release.

I was going to joke, “But John, what about your loyal Linux-using readers? How can we do this?” But instead, I’ll say that I’m glad that AdventureWorks is still alive and kicking. It is, on the whole, a nice demo database.

Leave a Comment

The Year in SQL

Published 2025-12-19 by Kevin Feasel

Anna Hoffman writes up the year in SQL:

For the FIFTH(!!) year in a row (my heart is warm with the number, I love SQL and #SQLfamily, and time is flying), I am sharing my annual Year in Review blog with all the SQL Server, Azure SQL and SQL database in Fabric news this year. Of course, you can catch weekly episodes related to what’s new and diving deeper on the Azure SQL YouTube channel (this blog post was livestreamed there too). This year, in addition to Data Exposed (52 new episodes and over 70K views!), we saw many new series related to areas like GitHub Copilot, SSMS, VS Code, and Azure SQL Managed Instance land in the channel, in addition to Data Exposed.

Click through for plenty of links around SQL Server 2025, Azure SQL, and Fabric SQL Database.

Leave a Comment

Optional Parameter Plan Optimization in SQL Server 2025

Published 2025-12-17 by Kevin Feasel

Tomaz Kastrun continues looking at new functionality in SQL Server 2025:

Part of new features in IQP (Intelligent query processing) is also OPPO – Optional parameter plan optimization – which refers to a specific variation of the parameter-sensitive plan (PSP) or Parameter Sensitive Plan Optimization (PSPO) problem in which the sensitive, parameter value that exists during query execution, controls whether we need to perform a seek into or scan a table. It is part of mitigating the parameter sniffing problem.

Read on for more information, as well as a demonstration of how it works.

Leave a Comment

What’s New in SSIS for SQL Server 2025

Published 2025-12-15 by Kevin Feasel

Chunhua Gu says, not much:

Security is a top priority for SSIS 2025, reflecting the broader enterprise’s focus on data protection and compliance. Microsoft.Data.SqlClient provides a modern, secure data access layer. This new provider supports advanced security protocols, including TLS 1.3 for encrypted connections, and integrates seamlessly with Microsoft Entra ID (formerly Azure Active Directory) for robust authentication.

In short, support the new-ish library (that has been around for several years), tie in with Microsoft Fabric, remove functionality that used to be in the product while spinning this as a grand new opportunity for developers to spend money on Fabric, and that’s it. Granted, SSIS hasn’t been a proper focus for the product since 2012 (sorry, Hadoop components in 2016—you’re out of the product now, so you don’t count), so all of this should come at no surprise.

Leave a Comment

REST API Invocation in SQL Server 2025

Published 2025-12-12 by Kevin Feasel

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.

Comments closed

Backups on Secondary Replicas in SQL Server 2025

Published 2025-12-03 by Kevin Feasel

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.

Comments closed

Upgrading to SQL Server 2025

Published 2025-12-02 by Kevin Feasel

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.

Comments closed

Thoughts on CPU Optimization and SQL Server Licensing

Published 2025-12-02 by Kevin Feasel

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.

Comments closed

SQL Server 2025 Now GA

Published 2025-11-19 by Kevin Feasel

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