Tag: Cloud Computing

  • Data Lost in the Cloud

    There’s been a war in the Middle East for many months now. As different countries battle, there have been attacks on infrastructure, including businesses that have facilities in the region. Among the casualties were a few Amazon data centers, and Amazon has acknowledged that some data is permanently lost. This isn’t to ignore the loss of life or horrific events, but for data professionals, where is a portion of this that is applicable.

    The cloud providers will group multiple data centers into Availability Zones (AZ), with some redundancy across zones to provide resilience. However, in this case multiple facilities were struck, and the damage exceeded what the AWS services were designed to withstand. Amazon did suspend billing in the affected regions, but that doesn’t necessarily help customers who were counting on data in the cloud. Note, the article discusses AWS systems, but Azure and GCP could have similar issues.

    While it’s unlikely that most of the AZs around the world would be engulfed in war, it is worth noting that none of the major cloud providers are doing anything to protect your data from catastrophe. For all the talk and marketing of “zones” and “redundancy”, there could be a wide-scale disaster that affects multiple places, and potentially renders data inaccessible in that region.

    Not necessarily all data, but it could cause problems with your data, which is what you should be concerned about.

    All the major cloud providers are susceptible to issues, and while they have implemented systems designed to tolerate failures, ultimately it’s your responsibility to protect data. Amazon warned customers when the first strikes occurred to copy or migrate data. I hope most customers did this, but I’m sure more than a few technical and managerial people thought AWS was fault-tolerant.

    AWS is, but there are limits.

    I wouldn’t abandon the cloud, nor would I stop trusting their backup services. I would, however, ensure I made some periodic copies of my data elsewhere. Losing a few weeks of data might be a major headache for many organizations, but losing all or most of your data might be something else entirely. Even monthly backups might mean the difference between a hassle and closed doors.

    Steve Jones

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

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

  • 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.

  • 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.

  • What is the Cloud?

    Last week we had a training session at Redgate Software on the Cloud. One of the first slides from John Q Martin asked the question, “what is the cloud?” The next slide had the answer: it’s just someone else’s computer.

    I mean that’s true, but it’s not Grant’s computer. He’s got a creaky, 4 year old HP that I don’t want running my workload.

    The cloud is many things, it’s hard to define, it does so much, and at the same time, can do so little for you. Except cost a lot. We certainly find no shortage of people spending a lot of money in the cloud and not necessarily happy about it.

    John was trying to educate others on the IaaS v PaaS, the challenges of cloud migration, giving them a perspective on what the cloud changes, and how customers think about the cloud. Apart from the basic details of what the cloud entails, he said an interesting thing (I’m paraphrasing here): the cloud does things that 95% of organizations couldn’t do themselves.

    It’s not just someone else’s computer. It’s a whole bunch of computers someone else owns and has put a lot of security, infrastructure, planning, tooling, and more to enable you to flexibly create systems at a pace you would struggle to match inside your organization.

    For most people.

    The cloud is amazing. It’s is someone else’s (large rack of) computers that you can rent. They will charge you for the flexibility, and they’re not doing all your work for you, but they give you the ability to configure things the way you want them. Or you can ask one of your buddies, Claude or Copilot, to set up the configuration for you.

    The cloud is a set of Lego bricks, some pre-built Lego models, a surface on which to place them, and a few rules to keep you from going too crazy, but you still have to do some work.

    The cloud is a great enabler for many things. Not all, and not always for those things, but it’s up to you to find where it works, where it doesn’t, and where it’s worth the money.

    That’s the cloud.

    Steve Jones

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

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