A Fine Slice Of SQL Server
Andrew Pruski hits a REST API:
The sp_invoke_external_rest_endpoint stored procedure that’s available in 2025 allows for SQL Server to hit external rest endpoints…which opens up quite a few interesting options.
I was thinking about this the other day and it occurred to me that Kubernetes has a REST API
But it’s not going to be trivial to hit, so click through for the steps.
Comments closedHaripriya Naidu digs into what’s new in SQL Server’s Resource Governor:
In this article, we’ll focus on how to control TempDB datafile growth using Resource Governor (RG).
- RG is disabled by default and available only on Enterprise edition.
- Until SQL Server 2022, RG could only manage user databases.
- Starting with SQL Server 2025, RG can now manage TempDB as well.
Click through for the demo and additional information.
Comments closedEd Pollack points out a new function:
With each version of SQL Server, there are always a few new features introduced that we applaud as we finally have access to a useful function that is already available elsewhere.
Introduced in SQL Server 2025 CTP 1.3, the PRODUCT() function acts similarly to SUM(), but multiplies values rather than adds them. It is an aggregate function in SQL Server and therefore operates on a data set, rather than on scalar values.
Ed notes that there are aggregate and window function versions of PRODUCT() and shows examples of how it works.
Brent Ozar shares the numbers:
In this quarter’s update of our SQL ConstantCare® population report, showing how quickly (or slowly) folks adopt new versions of SQL Server, the data is very similar to last quarter. SQL Server 2019 still rules the market:
Click through to see where people are at in Brent’s sample of the market. Alan Cranfield has some numbers for SQL Server on AWS and those come pretty close to what Brent’s sample shows as well.
Comments closedBrent Ozar looks under the covers:
When CTP 2.0 came out, I blogged the thousands of new feature flags, messages, and system objects in SQL Server 2025 CTP 2.0, and I haven’t had the time to dig more deeply into those yet. In that post, I discussed the new sys.dm_feature_switches table, and I mentioned that it might disappear before release. Indeed it has – last week’s new CTP 2.1 removed access to that table, meaning that was probably our one-time shot to get a glimpse into something cool and undocumented. I would have loved to have been a fly on the wall when folks at Microsoft read my blog post and realized they’d left that table unguarded and publicly visible, hahaha. I love my job.
So now CTP 2.1 is out, and it comes with a few things I think you’re going to be interested in.
Read on to see what Brent has found.
Comments closedEd Pollack gives us the lowdown:
Columnstore indexes are a powerful tool for storing analytic data directly in SQL Server. This feature has improved in every version of SQL Server since their inception over ten years ago, and SQL Server 2025 is no exception!
The newest enhancements are laser-focused on business continuity and performance. Ordered clustered columnstore indexes, ordered non-clustered columnstore indexes, and database/file shrink operations are all given significant boosts that are worth the time to introduce and learn.
In this article we will dive into each of these changes, how they impact columnstore workloads in SQL Server, and demonstrate their operation.
Read on to see what we’ve got. Nothing in here is ground-breaking, but it’s a set of nice quality of life improvements.
Comments closedKevin Hill disambiguates product offerings:
Let’s break down the main SQL Server editions: Express, Web, Standard, and Enterprise as well as what makes each one different. Not just in features, but in what they let you do… or stop you from doing.
Click through to learn more about each edition, what it offers, and what official limitations exist.
2 CommentsJordan Boich points out something interesting coming in SQL Server 2025:
Accelerated Database Recovery (ADR) was introduced in SQL Server 2019. Its main purpose is to allow for faster database recovery in the event of a crash or unexpected shutdown. Traditionally, the database engine handles crash recovery through a series of phases—analysis, redo, and undo—which can be inefficient and slow, especially when dealing with long-running transactions.
To make a long story short, ADR “shortcutsˮ the recovery process by introducing a new approach to handling undo operations. Instead of relying heavily on scanning the transaction log—which can be painfully slow for uncommitted or long-running transactions—ADR maintains a version store within the user database to track row-level changes. This allows SQL Server to quickly roll back uncommitted transactions without scanning the entire log. The result is much faster crash recovery, quicker rollbacks, and improved overall database availability, particularly in high-transaction environments.
Read on to see what’s new, as well as some of the consequences of enabling this feature.
Comments closedAlexander Korotkov reminds us that there are a lot of data platform products out there:
In a recent Hacker News discussion, there was some confusion about the differences between OrioleDB and Neon. Both look alike at first glance. Both promise a “next‑gen Postgres”. Both have support for cloud‑native storage.
This post explains how the two projects differ in practice. And importantly, OrioleDB is more than an undo log for PostgreSQL.
Alexander is the creator of OrioleDB, so price in any vendor bias you wish as you see the comparison of two up-and-coming technologies.
Comments closedLaurenz Albe takes a peek at an upcoming feature:
Everybody wants good performance. When it comes to the execution of SQL statements, accurate optimizer statistics are key. With the upcoming v18 release, PostgreSQL will preserve the optimizer statistics during an upgrade with dump/restore or
pg_upgrade(see commit 1fd1bd8710 and following). With the beta testing season for PostgreSQL v18 opened, it is time to get acquainted with the new feature.
It’s kind of wild to me that this wasn’t in place years ago for PostgreSQL.
Comments closed