Author: way0utwest

  • Great Things

    “Great things are done by a series of small things brought together.” – Vincent van Gogh, Dutch Post-Impressionist Painter.

    I ran across this quote recently and it struck me that it’s expresses a thought I’ve had for some time. Instant, magical success isn’t often what it appears. Anyone that seems to have sprung up overnight with success in anything has often spent a lot of time getting ready.

    Outside of lottery winners, of course. If you bought a ticket, that’s instant success. Unless you buy a dozen every week, then you’ve likely been doing your own (poor) preparation over time.

    Whether it’s software, sports, business, anything that takes off, goes viral, or suddenly catches the public’s collective eye is the result of a lot of small things. Practice, learning, continuous improvement. It’s a formula that works in music, in sports, in manufacturing, and in software.

    Perhaps the most important part of this quote is the ending. Things have to be brought together. In software, we work in teams, and we have to coordinate and collaborate. Whether with other human developers, AI agents, or Operations. We have to learn to ensure our efforts, our knowledge, our evolution works together. This might be especially important in ensuring database and application code changes mesh well. That’s becoming a concern for more organizations, and more management that realizes that the database has to become a part of the software development life cycle. Either developers need to learn more, or work closer with database staff.

    We can do great things, we can build amazing systems, but it takes effort, and it takes teamwork.

    Steve Jones

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

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

  • Cleaning Up Azure MS Defender Billing

    I have a few Azure subscriptions, which are fairly small and not used that often. Mainly I do some SQL Server or Azure SQL experimentation. Sometimes I might create another resource, but I try to not waste resources and disable them quickly (or drop them) when I’m done.

    However.

    I hadn’t done much in the last couple of months on Azure. For some reason, I decided to check my bill. What I found was that there were charges for $35-ish/month. This is within my free credit limit as an MVP, but that seemed high. I have a few serverless dbs and some storage, but I was expecting more of a $15 charge.

    I decided to investigate. I started with the Billing section, where I saw that Microsoft Defender was swamping the charges in my bill. I don’t remember enabling this, and typically skip this stuff since I work with test data and nothing sensitive.

    2026-10_0159

    As you can see, the Defender items are charged, but not linked to a resource?

    WTF? How do I debug this? I have a small subscription, maybe a few dozen resources. Imagine you had a larger estate? I decided to ask Copilot. I get this result:

    2026-10_0146

    OK, environment settings, let’s check the items under here.

    2026-10_0147

    Now, where is this enabled? I checked the Defender properties for the subscription.

    2026-10_0148

    I went into the various Azure SQL databases, clicked the Security section for Defender and I keep seeing nothing enabled.

    2026-10_0160

    I’m ready to open a case, and waste the days and then multiple contacts trying to work through this with some customer service person in another time zone, who reads docs.

    Digging further, I keep clicking around, Copilot being of no use here. I eventually start clicking in every resource, and I get to the logical server for my Azure SQL Databases. Here’s where I see it, at the server-level.

    2026-10_0154

    I don’t think I turned this on, but perhaps I tested something.

    In any case, I click settings and then disable Defender.

    2026-10_0155

    I’m less concerned that this got turned on, because I might have done that. I would love some auditing of actions to determine this, as I could see someone else in my team (if my team were bigger than me and the 3 dogs) trying this out. I’d want to know who to talk to about changing settings.

    More, I’m annoyed that the bill doesn’t link to resource settings, or that this being enabled at the logical server level isn’t reflected and noted at the database level.

    This was a 45 minute investigation that should have taken 3, so a word of warning to you Azure users. Be careful what you enable, and when you have billing issues, check the resource group and logical servers, in addition to your databases.

  • PostgreSQL 19 Is Late

    “All software contains bugs.”

    That’s a quote from Robert Haas’s “Postgres 19 is late” post. He goes on to say that PostgreSQL has lots of bugs in it. It’s the way it’s been for a codebase that’s over 40 years old. He goes on to note that it’s easier to find bugs with LLMs, and easier to fix them. It’s not, however, as easy to do the latter as the former.

    The impact on PostgreSQL 19 is that they’ve had to revert a number of features much later in the process because the humans were reviewing and fixing bugs found by LLMs. This effort delayed other work and has affected the release.

    As someone who primarily works with SQL Server, I’m not that worried about delays in PostgreSQL or other platforms. I think it’s a fine choice, but I’m focused on SQL Server, which I think is more of a joy to work with.

    However, there are a few interesting things in here. First, I think SQL Server has had a lot of bugs found lately (likely by AI LLMs). I recently wrote about the frequency of patches, which is higher in 2026. This is probably due to LLM code review, and that’s good. It also means we likely will have more patches coming, not just in SQL Server or PostgreSQL but also in our other systems. What’s the likelihood that someone will run an AI review and find bugs in other COTS software, internal apps, or even those no-code/lo-code systems people have been deployed? That’s not even mentioning the vibe-coded prototypes that are suddenly important enough to put into production.

    The other interesting thing was that Robert accepts that LLMs are likely to find more bugs in the future. How will they find time to work on them? After all, from the article, fixes “still need to be reviewed and committed by humans.”

    Maybe the best part of the last paragraph. He says LLMs are going to require every developer to raise their game. Every feature is going to be scrutinized by AI. That’s a challenge and an opportunity, but the key is that developers need to get better. AI can help you and write code at amazing speeds, but it doesn’t think.

    We need sharp developers that think in order to cope with AI.

    Steve Jones

  • A Heavy Heart

    Hugo, I have many memories of moments we spent together, discussing data, career, life, and family. Three stand out, though not more or less important than any others.

    I can remember asking you a question years ago at a SQL Saturday about the way an execution plan was formed, and you patiently explaining to me something I didn’t understand. I’m sure I asked some poor questions, but you tried your best to help me understand some aspect of why the plan was shaped a certain way. Your patience and exuberance still stand out in my mind today. You trying help me understand something that I’m not sure I understand to this day.

    We caught up at one of the MVP Summits at night, at a time when our children were approaching the end of secondary school education. We had a common thread in theater, brought to us by our (not-so) young ones, and I recollect the pride with which you talked about your kid performing, me feeling the same way about mine.

    At the PASS Summit, I gave a career talk a long time ago, and you came up to me at the end. You told me I hadn’t said anything you didn’t know, which made me feel a little as if I’d failed. You then told me I’d presented it in a way that made you think and inspired you to think about doing something differently. I was amazed that I’d touched someone like you, who I felt had already succeeded.

    Hugo Kornelis has been one of the SQL Server experts who have helped, shared, inspired, and taught many of us over the last few decades. He runs SQLServerFast.com, where he provides a wealth of training, both free and paid (support him, buy a course). He’s also been battling leukemia for a few years, and recently posted Game over, as his fight has taken a turn for the worse. Hugo has faced this challenge by fighting with grace and honor in a way I’m not sure I would, or many have. I kept hoping he would keep improving and I’d have many more opportunities to see him. Grant and I have agreed to take over hosting his site, with support from Redgate, and I’m not happy about it. I wish I didn’t have this opportunity.

    I’d much rather have more conversations with Hugo.

    Just typing that line brings tears to my eyes. Hugo has been a friend, a mentor, a teacher, a joy to chat with, and an easily spotted man in a crowd with his trademark blond streak. I was thrilled to come over to Belgium right after the pandemic and spot that blond streak above a mask, knowing I’d have another chance to spend time with him.

    Life is short, and I’m acutely aware of that as I age. I will cherish the words and moments I’ve shared with Hugo and hope I get the opportunity for more. Fingers crossed his fight continues for the foreseeable future.

    Steve Jones

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

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