Voice of the DBA

Author: way0utwest

Monday Monitor Tips: Virtual Machine Usage and Cost

One of the things I’ve been requesting for a number of years is cost information. I could see this coming in 2015 with the move to the cloud and need to justify the resources provisioned along with sizes. Doing that effectively needs cost information.

Redgate Monitor has added a bit of cost information, and the virtual machine section in the Estate tab contains this. This post looks at what is available (as of June 2026).

This is part of a series of posts on Redgate Monitor. Click to see the other posts.

Virtual Machines

When I first started managing VMs and moving database loads to them, one of the things that I was concerned about was the CPU and RAM usage. CFOs and lots of admins wanted these are 100% to get the most out of their investments.

I wanted something less to prevent my phone from ringing constantly.

When you pick select the Estate tab, you see a number of items, but since v143.0.2906, there is a Virtual Machines item.

If you select that, then you see all your virtual machines, along with the resource name, group, and various metrics. This is a quick overview of what’s running.

If you look at the list, some are local and some are in the cloud. In addition, to the right, I see the metrics that help me understand average usage in a few ways: CPU, memory, storage allocated and used, and costs.

There aren’t any costs above as we filter that on the demo site, but if you provide cloud credentials, we use this to get some cost information. Here’s a shot from the doc site, which shows the costs in local currency (pounds Sterling for RG) and USD, which helps normalize the costs. You can read more about this on the doc page.

If you select a machine, a blade slides out with more details on usage. Here you can see the primary SSC server. This helps me decide if this is over or under provisioned based on data. I see CPU usage across a month, along with memory and storage (not shown).

If I click the “compare with” toggle, I see the last two months overlaid, which is useful info. This helps me decide if last month was normal or an outlier. It does seem like June was a busier month than May, which is good. My boss likes busier.

As far as data, I have choices for the period, going from the last day to 6 months.

It’s up to me to keep this data, and I have an entry as well in the Data Retention settings for this data.

There’s more coming, and I know there are plans to add PaaS data as well, but if there are things you’re interested in, please contact your account rep and let them know what needs you have and why. I think this is an important aspect of monitoring that will grow over time.

Summary

This post showed the first slice of work on costing information, with an emphasis on virtual machines. There is performance as well as cost data, so you can evaluate whether you are appropriately sized for your systems.

I’m looking forward to more information, including custom costs being added for on-premises machines, as well as PaaS services.

Redgate Monitor is a world-class monitoring solution for your database estate. Download a trial today and see how it can help you manage your estate more efficiently.

June 29, 2026
Is Fabric a Reliable Service or a Ripped Resource?

Over the last few weeks, I’ve noticed a few complaints from different friends and customers about issues with Microsoft’s Fabric service. I had assumed these were isolated incidents in just a few places, and customers were being refunded according to an SLA. Then I saw Joey D’Antoni’s post this week about Fabric going down. It lists quite a few of the incidents in June, including a few global ones.

However, the most surprising thing in the post was this link, noting Fabric doesn’t have a dedicated SLA. Instead, it’s under the general Microsoft support agreement, meaning your organization needs to have a support plan to get help. I think that makes some sense, but I’d really expect that a data service in the cloud, including an analytic service that touts itself as real-time, would have a high SLA. Some agreement on the order of 4 9s at least, if not 5.

For those of you who think you can do better on premises, I’ll remind you that four 9s mean you get 52 minutes of downtime a year, or 1 minute a week (roughly). Five 9s is 5 minutes a year, and the weekly calculation doesn’t matter. I’ve had systems run for a year, but a lot, and not a lot of databases, especially with patching 6 times a year. This year, with AI (my guess) finding lots of holes and GDR releasing quite often, I would guess that three nines is out the window for most SQL Server systems that aren’t HA clustered in some way.

As a point of reference, Denny notes that Azure SQL database, Business Critical, has a four-and-a-half 9s level of reliability and financial refunds for costs if that’s exceeded. You will need some sort of business insurance if you worry about revenue issues, but my guess is that most of us live with the downtime and work around it (and hopefully, plan for it).

I’ve been skeptical of Fabric (outside of Power BI). It feels cobbled together, so many issues are reported, and I feel like it’s immature. If I were working on a new analytics project, and we didn’t have a solution, I might PoC it, but I’d be more likely to consider Databricks, Snowflake, or Redshift rather than Fabric.

Perhaps you have a different view, or you have had success with Fabric. I know some people who have, but it seems one-sey two-sey and not commonplace. There seem to be so many workarounds and issues; it makes me skeptical that Fabric is really ready for primetime if Microsoft won’t stand behind it. Databricks only gives credit up to three 9s, but if they fall below 95%, they issue a 100% credit. Snowflake offers four 9s.

I feel that if Microsoft were confident in their reliability, they’d offer refunds if they didn’t perform.

Steve Jones

June 27, 2026
I Want to Use My Brain

I had a very interesting conversation recently with a longtime DBA who was worried about using AI in their database work. The Redgate State of the Database Landscape 2026 report showed that the vast majority of you (99%) are getting value from AI, so clearly it’s being used. However, this individual was concerned that using AI for tasks would not engage their brain, and they might lose some of their SQL skills.

And they want to use their brain at work.

I would hope most of you want to use your brains and accomplish things. That’s a lot of the reason I continue to work and enjoy what I do. It engages me, and I find the challenge of solving problems to be interesting work. Whether that’s simple T-SQL queries, architecture for an application, or the culture challenges of changing teams. It’s exciting to move anything forward.

I would hope most people want to use their brains at work and not just get through the day without straining their mental faculties. It’s fun to solve a problem, puzzle, or challenge. The thing I’ve learned is that AI doesn’t preclude that.

I use AI to tackle tedious things. Small things. Minute-saving things. The number of times I use an AI to do something that saves me minutes is surprising. Those minutes add up across the week and let me avoid some of the tedious work and focus on the things I enjoy: deciding if something works and if it is the appropriate solution.

I might ask an LLM to generate some code, summarize some text, or give me a first draft. I might use a lot of what I get, or just a little. I might throw everything away and do it myself, but often that little kickstart gets me moving quicker than I might otherwise get started, and it’s lower stress for me when I’m on a deadline.

I enjoy PowerShell, but sometimes the tedium of getting the syntax right and formatting things is annoying. Scaffolding around an algorithm can be a pain. An AI can do a lot of that stuff and I can evaluate the result. I never type > instead of -gt anymore because the LLM does it. I decide if I like the approach or not, or if I want to write a little code inside the scaffolding.

I still use my brain. AI hasn’t changed that. It’s just that I avoid some of the tedious things. And if I need a break, I can go for a walk or cook or play guitar rather than slogging through a chore that isn’t interesting.

Steve Jones

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

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

June 26, 2026
Advice I Like: Respect

“Don’t aim to have others like you; aim to have them respect you.” – from Excellent Advice for Living

This is an interesting piece of advice. It’s easy to look at this and think, no, that’s not what I want, but remember that these two things are not mutually exclusive. People can respect and like you. However, for many things in life, you really want respect more than link.

When I coach, respect is more important. At work, respect is more important. In relationships, they’re probably equal.

Respect means that people listen to you, treat you well, give weight and consideration to your words, actions, and feelings.

I like some people, but don’t respect them. I might enjoy spending time with them, but our relationship is more for leisure and fun. We don’t really have anything of significance between us. We can just enjoy time.

Your goal is respect.

I’ve been posting New Words on Fridays from a book I was reading, however, a friend thought they were a little depressing. They should be as they are obscure sorrows. I like them because they make me think.

To counter-balance those, I’m adding in thoughts on advice, mostly from Kevin Kelley’s book. You can read all these posts under the advice tag.

June 26, 2026