Press "Enter" to skip to content

Day: January 26, 2026

Azure Pricing and Exchange Rates

Thomas Rushton troubleshoots a billing issue:

So you signed up for a three year deal to keep costs down and more predictable.  But while Reservations can make Azure spend more predictable, they can’t make it completely static. You’ll be OK if you’re paying in USD, but if your organisation is billed in any other currency, you’ll be subject to the vagaries of exchange rates when buying any Azure service. 

Read on for a specific instance in which UK customers experienced a fairly significant price change based on the timing of changes in currency exchange rates.

Leave a Comment

Thoughts on the Future of MySQL

Dave Stokes shares some thoughts:

 I am not intentionally trying to upset anyone with this blog post or minimize the efforts of many brilliant people whom I admire. However, I connected with several people over the 2025 holidays who all had the same question: What is the future of MySQL? At the upcoming FOSDEM conference, several events will discuss this subject and push a particular solution.  And in several ways, they are all wrong.

Oracle has not been improving the community edition for a long time now. They have laid off many of their top performers in the MySQL group. We got almost a good decade and a half out of Oracle’s stewardship of the “world’s most popular database”, and we should be thankful for that. However, now that time is over, it is time to consider future options that will involve no updates, CVEs, or innovation for what is the MySQL Community Edition.

Read on for a few possibilities, focusing on the open-source database market.

Leave a Comment

Adaptive Joins and Large Memory Grants

Kendra Little re-creates a problem:

Adaptive joins let the optimizer choose between a Hash Join and a Nested Loop join at runtime, which can be fantastic for performance when row count estimates are variable. Recently, when Erik Darling taught two days on TSQL at PASS Community Data Summit, a student asked why a query plan where an adaptive join used a Nested Loop at runtime ended up with a large memory grant anyway.

I didn’t remember the answer to this, but the great thing about co-teaching is that Erik did: adaptive joins always start executing as Hash Joins, which means they have to get memory grants upfront. Even if the query ultimately switches to a Nested Loop at runtime, that memory grant was already allocated. This has real implications for memory usage, especially in high-concurrency environments.

Read on for a dive into adaptive joins, how they work, and the consequences when the database engine makes use of them.

Leave a Comment

Collation Conflicts and tempdb

Greg Low sorts out an issue:

I see these issues all the time. Developers create applications that require specific collations at the server level, because they don’t handle temporary tables (and by extension) tempdb well.

All this can be avoided, and you can easily build applications that will work with temporary tables, without worrying about the server (and tempdb) collation.

Read on to learn more about the problem and what you can do to mitigate it.

Leave a Comment

SQL Server Container Startup Scripts

Andrew Pruski notices a change:

Hmm, ok we have a script /opt/mssql/bin/launch_sqlservr.sh and then the sqlservr binary is called.

I swear this wasn’t always the case, have I seen that before? Started to doubt myself so spun up a pod running an older version of SQL (2019 CU5) and took a look: –

It looks like this was a somewhat recent change, but with it comes an interesting new capability that Andrew shows off.

Leave a Comment

Solid Black Icons in Power BI Desktop January 2026

Marco Russo clues us in on a bug:

In mid-January 2026, many Power BI Desktop users began noticing a strange visual regression: several icons in the interface—including the Data, Model, and DAX icons—appeared as solid black shapes instead of their normal outlines. The issue appeared suddenly, even on machines where Power BI Desktop had not been updated. Because it happened the same week that Power BI Desktop January 2026 was released, this led to understandable confusion.

The root cause was not Power BI Desktop itself but an unexpected regression in the WebView2 runtime, one of the external dependencies used to render parts of the UI. Microsoft confirmed the issue and is preparing an official fix.

Marco does have a temporary fix that works until Microsoft has the official fix in place.

Leave a Comment

Removing a Supersized tempdb File

Jeff Iannucci wants to smooth things out:

While reviewing the configuration of a client’s SQL Server instance recently, I noticed that they had a very curious tempdb configuration. Although it had multiple files for the eight CPU cores as Microsoft recommends for tempdb configuration, it also had another MUCH larger file with a MUCH larger growth rate.

And it turns out that when this happens, there are some knock-on effects that make it a challenge to remove such a file later. But read on for the solution.

Leave a Comment