Author: way0utwest

  • Pay for Performance

    There’s a new TPC-H benchmark from Microsoft; this one running on cloud infrastructure in Azure. It’s the top-performing SQL Server benchmark at the 1TB level, getting to 1,667,428 QphH (roughly queries per hour). This value exceeds the next highest on-premises setup from HPE, which has 1,531,016 QphH@1000GB. This is the 2nd-ranked TPC-H benchmark, though the top slot is from an Exasol database.

    Notably, the benchmark comes in at $558.17 in the Price/QphH price performance column. The other SQL Server systems are in the $200-ish range (from $192.37 to $263.13). That’s quite a difference in price, and it might dissuade some of you from moving to the cloud instead of running a large on-premises setup. That’s a point of concern, especially as the cost of the cloud has become an issue in many organizations.

    There’s a blog post from Pam Lahoud that outlines the effort to get this benchmark audited and approved. Part of the post notes that the rules for the benchmark mean that public pricing needed to be used. This is the spot, pay-as-you-go pricing, which is the most expensive rate. The storage was also configured with the maximum capabilities, which weren’t needed. She notes that the hybrid benefit for moving licenses isn’t available, which I’m not sure makes much of a difference, but it might. Pam does note that the licensing was priced at 3 years of the Pay-As-You-Go level, which is 2/3 of the cost.

    There are likely ways to optimize costs, and there is the promise of a future blog that covers how you might size and price what you need for a workload. I’m sure there are savings to be had, though it remains to be seen if you could get a price lower than that of the on-premises systems. Don’t forget that the on-premises systems might have other savings from a different approach there as well.

    The cloud, in many cases, is expensive. If you want to get great performance out, then the people whose computer you decide to rent will likely charge you a premium. Perhaps you can gain some savings with flexibility, shutdowns, resizing, and more, but that really depends on your being able to take advantage of the flexibility of the cloud. If you have a steady workload, or one that has to run most of the time, you’ll likely be paying quite a bit.

    Steve Jones

    Listen to the podcast at Libsyn, Spotify, or iTunes.

    Note, podcasts are only available for a limited time online.

  • Flyway Tips: More Object History

    I wrote about Flyway Desktop Object History in a previous tip. This feature has been enhanced, so I wanted to write an update.

    More History

    The changes now can be looked at from a project level. Note the new history button at the top of the schema mode. This didn’t exist in the previous post.

    2026-11_0222

    If I click this, I get the same view of committed and uncommitted changes, but from a project view. You can see there are two changes in this commit, whose hash is in the far right, a little hidden near the bottom of this image.

    2026-11_0223

    Some commits have a lot of changes, but I can click a change to see the diff. In this case, I can see in the 5th item, the Address table.

    2026-11_0225

    This is great for standups, or a quick look without searching in the repo for commits. Here I see some level of work done, by me and others, which is useful when coordinating a team.

    Summary

    This an improvement of an existing feature, and I like the direction. I’ve asked for the commit to move, so I can easily see it, but otherwise, this is a nice way of seeing how my repo has changed over time. The schema model is especially important here.

    If you work with Flyway, update your desktop and give it a try. We would love to hear your feedback.

    Flyway is an incredible way of deploying changes from one database to another, and now includes both migration-based and state-based deployments. You get the flexibility you need to control database changes in your environment. If you’ve never used it, give it a try today. It works for SQL Server, Oracle, PostgreSQL and nearly 50 other platforms.

  • Helping an English Student with R

    I got an interesting message from my daughter recently. She’s doing graduate studies in Belgium at KU Leuven. Her field is literature and linguistics, and as part of that, she has to analyze various writings. While visiting with her last month, she mentioned that her professor was using R (R Language) and giving them scripts to run to look at language usage.

    The other day she texted that her R script wasn’t running and could she get some help. She was a little intimidated to ask the professor why the script didn’t run on her laptop, when she saw it running in class on the professor’s machine. I had some time, so we started a screen-sharing session on WhatsApp, which is amazing. Side note, I can’t believe I can talk with my daughter and watch her work on her computer in real time, with a few clicks of a button.

    In any case, she told me she was getting a file size error. She couldn’t load a 32MB file because the RStudio limit was 5MB. That seemed a little funny to me, as I’ve had some large files loaded into RStudio. My suspicion was that this error was masking another problem, but I watched my daughter work to see.

    What she had done:

    1. download a zip file
    2. extract this to a new folder in Documents
    3. open the R script in RStudio
    4. drag the text file for analysis into RStudio

    That seemed strange. In looking at her script, I realized there was likely a pathing issue. We ran a getwd() and then a setwd() to experiment. We got a different error, which looked to me like a collation/formatting issue. We added a fileEncoding parameter to read.delim() and the script started working. She was amazed and pleased.

    Explaining the technical aspects of this to an English(ish) student, and helping her to lightly understand what to do was interesting. She made notes in a file on using setwd(), changing backslashes from Explorer to forward slashes, and how to add the parameter to the various read commands. Ultimately, she was back to being productive, without learning much about R or technology, but having a path forward of things to try when something broke, with notes saved in a document.

    It reminded me of myself when I’m trying to fix something on the ranch I’ve never done before. I have to quickly learn what’s wrong, how to troubleshoot the extent of the issue, and decide how to move forward. Those troubleshooting skills are invaluable, and that’s likely the biggest thing my daughter learned. That’s what I think is a struggle for many people, in all fields, but certainly in technology.

    The next time you get a chance to help someone troubleshoot, work with them, explain your process, and help them improve for the future.

    Steve Jones

    Listen to the podcast at Libsyn, Spotify, or iTunes.

    Note, podcasts are only available for a limited time online.

  • A New Word: Semaphorism

    semaphorism – n. a conversational hint that you have something personal to say on the subject but don’t go any further – an emphatic nod, a half-told anecdote, an enigmantic “I know the feeling” – which you place into conversations like those little flags that warn diggers of something buried unerground: an unexploded bomb, a sacred burial ground, or a high-voltage cable that secretly powers your house.

    The longer I work with customers in different environments and present at different events, the more I hear lots of semaphorisms from different people. They hint and half-tell war stories of things that are broken.

    These could be technical things or cultural things. Those items that frustrate you or embarrass you, or maybe are just maddening to you. Often these are things that you might not want to completely disclose, but just provide enough info that the rest of us an empathize.

    Or be glad we’re not experiencing them.

    From the Dictionary of Obscure Sorrows