Press "Enter" to skip to content

Day: October 14, 2026

A Statistical Error

Hugo Kornelis tells a story:

Anyway, the load process at this customer had multiple steps. Truncate and then fill staging tables with the current data from various source systems. Use the data in those staging tables to update the first of the data vault tables. And then use a join between the same staging table plus the just updated data vault table, with a filter on the current date, to update all other data vault tables.

With some of the tables having more than 500 million rows and over 50 columns, this process needed some time. But that was not a problem. The load finished before the offices reopened. Usually. But not always. Sometimes, it would run a few hours longer. And nobody knew why the load would take extra time at those seemingly random moments.

Read on for the full story. It’s a sobering reminder that each environment is different, and something that worked really well in one environment may fare poorly elsewhere.

Leave a Comment

Improvements in the Microsoft Fabric Capacity Metrics App

Reitse Eskens is pleased:

In case you missed it, Microsoft released a new version of the Metrics App. We all know the current one, and we have opinions on it. But it’s all we’ve got from Microsoft, so we made do.

But now, there’s a new one. Or, well, a new one. When you install a new version, you get a second option!

Click through to see this new app, currently in preview. I wonder if it still requires the same level of permissions to see the contents. I recall that being a sticking point for capacity optimization in Fabric, especially when you bring in consultants who can understand the app but aren’t allowed to see it because of the necessary permissions.

Leave a Comment

Running SSIS Packages in Microsoft Fabric

Koen Verbeeck performs some ETL:

We have a large on-premises ETL solution built with Integration Services (SSIS). We are building a new data platform in the cloud using Microsoft Fabric. While we are building this, we would like to migrate the existing SSIS solution to the cloud so we can decommission our old servers. Is there an option to run SSIS packages in Fabric?

Click through for the answer, which is a solid “maybe, just so long as it fits this exact pattern.” But as Koen explains, some of the restrictions will hopefully go away as the feature matures.

Leave a Comment

The Trade-offs of Indexing

Rob Farley thinks about costs and benefits:

“How do you weigh the risk vs the reward of your database design decisions?” asks my old friend Pat Wright. And one of the examples he gives is around indexes. I like indexes, so let’s talk about some of the choices when you’re thinking about adding a new index. And for the sake of simplicity, a new nonclustered rowstore index.

A new index might make an expensive query be much faster. Users might feel like the application has become much snappier. But a new index is not free.

Read on for Rob’s thoughts.

Leave a Comment

The Power of Group Managed Service Accounts

John Sterrett gets rid of a password:

Somewhere in your environment, a SQL Server service account password hasn’t changed in years. Several people know it, and it’s probably in a script or a spreadsheet. I wouldn’t be surprised if someone hasn’t even put it in an AI chat.  Group managed service accounts (gMSAs) remove that problem.

This past weekend, during my Advanced Security Protection talk (online version you can watch) at Days of Data in Pittsburgh, someone asked: “What are the best practices for encrypting passwords in connection strings?” That reminded me I’m overdue to blog about Group Managed Service Accounts, so here we are, because the best way to encrypt them is to not need to encrypt them.

This does get a lot trickier if you’re not on Windows, and it does require Active Directory. But for most environments, gMSAs are an outstanding idea.

Leave a Comment

Keeping Documentation with Code

Andy Mallon shares some advice:

For years, I’ve advocated for keeping developer documentation in the same code repository as the code it describes. In the age of AI, that practice has become even more important.

The reason is simple: the easier we make it to maintain documentation, the more likely it is to stay current.

I do agree that having documentation live separately from code, most of the time, leads to outdated code. But then again, having documentation live with the code, most of the time, also leads to outdated code.

Leave a Comment