Voice of the DBA
A series of episodes that look at databases and the world from a data professional's viewpoint. Written and recorded by Steve Jones, editor of SQLServerCentral and The Voice of the DBA.
info_outline
Cognitive Coverage
06/30/2026
Cognitive Coverage
Satya Nadella talked about cognitive coverage in the age of AI, about being able to understand and manage AI agents to get work done as a software developer. covers the future of work and comfort in this new age. This reminds me of a book that recommended, . I love the book, but it's slow reading as I constantly stop and think. Work is changing; it's becoming unbundled and re-bundled in different ways, and many of us will have to learn to work in new ways. Not all of us, but many of us. Some might see their day-to-day efforts change little; some will not recognize their job a year from now. As with anything, lots of us will be in the middle with some changes, some status quo. That's certainly where I am with AI assistance. Read the rest of
/episode/index/show/voiceofthedba/id/41810375
info_outline
SQL Server Still Wins
06/28/2026
SQL Server Still Wins
Is it worth continuing to run SQL Server when PostgreSQL licensing is zero? Rebecca Lewis has a that looks at some of the pros and cons of paying for SQL Server instead of moving to PostgreSQL. She starts with some of the things PostgreSQL does well, of which I think the Extensibility is really cool. SQL Server has some of this in CLR and the non-SQL language support, but those seem kludgy and complex to me. They aren't really integrated into the SQL Server platform. They're good, but I do wish vendors or the community could add some extensions in a way PostgreSQL does. Of course, I also worry about stability, so maybe this is a wish that isn't really a great idea. Read the rest of
/episode/index/show/voiceofthedba/id/41729090
info_outline
I Want to Use My Brain
06/25/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. Read the rest of
/episode/index/show/voiceofthedba/id/41728955
info_outline
Spending Time in the Office
06/23/2026
Spending Time in the Office
I've visited a number of customers in the last few years who require most people to work in the office. Recently, I had the chance to go to Epic Systems, just outside Madison, WI, USA. They are a medical records software provider that was very reminiscent of Microsoft in some ways, and quite different in others. I published a blog with some pictures, so you can see how cool this office is in person. Epic has all their employees coming into the main office every day. They are flexible if you have needs, but the expectation is that employees go in every day. I believe this is also their policy, and culture, in various offices around the world. Read the rest of
/episode/index/show/voiceofthedba/id/41728850
info_outline
What is the Cloud?
06/21/2026
What is the Cloud?
Last week we had a training session at Redgate Software on the Cloud. One of the first slides from 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. Read the rest of
/episode/index/show/voiceofthedba/id/41693625
info_outline
Changes, Happiness, and a Few Tears
06/18/2026
Changes, Happiness, and a Few Tears
Change is inevitable for most of us. The jobs we hold, the places we work, the people we know, even our families grow and change over time. As I get older and live longer, I've learned to accept, appreciate, and flow with changes. I might resist, delay, embrace, or anticipate tomorrow, knowing there is always a positive and negative side to things. This week, one of my colleagues retired. Annabel has been a part of nearly as long as I have, and we've worked together for many years. If you've ever attended a , live or online, she likely had a part to play in the planning, organizing, execution, financing, and every other part of the process. Read the rest of
/episode/index/show/voiceofthedba/id/41693195
info_outline
Follow Your Hunch
06/16/2026
Follow Your Hunch
For a while, I kept seeing that . So many people felt that with an AI LLM, the costs would go way down to produce software. I'm not sure that's true. In fact, some companies are finding they . However, the ability to produce more code, experiment with ideas, or generate proof of concepts has gone up. Whether it's worth the cost or not depends on the engineer, but some organizations are finding that they can try more things than they would ever had time to try in the past. The time of engineers was the constraint, and if you can afford the cost, AI LLMs can relieve that time pressure. Read the rest of
/episode/index/show/voiceofthedba/id/41576860
info_outline
The Slow Growing Problems
06/14/2026
The Slow Growing Problems
Both as a DBA and developer, I've had plenty of immediate, this-is-broken, fix-it-quickly issues. Usually, I, or someone else, wrote some bad code and somehow got it deployed. I mean, I do test things, and I would (probably) never change code after I'd tested it to fix that one little annoying thing, like the formatting. I'd (almost) never do that, and I'm sure you wouldn't either. Yet somehow bugs slip in at times. Those are the acute issues, and they can be hard to fix at times, but often we can reproduce the problem in development and build a fix. Sometimes we even spot the issue quickly and just fix it in production. I'm sure you never do that, but I have had that experience myself a few times. Read the rest of
/episode/index/show/voiceofthedba/id/41576775
info_outline
Would You Retire Rather Than ...
06/07/2026
Would You Retire Rather Than ...
is the creator of C++. I read a few of his books and alternately loved what he'd done and hated having to write C++ code in university and at a few jobs. I found it tedious and hard, though arguably better than C once you had a decent set of classes structured. BTW, I love his website, the basic text view of the world, which is how I have built a few sites on my own. I caught an interview with him and . He had this quote: "Senior developers are already retiring rather than deal with it." He doesn't love the results from AI, which is fine. And it's not what I want to talk about today. Read the rest of
/episode/index/show/voiceofthedba/id/41510930
info_outline
The Data Model Matters
06/04/2026
The Data Model Matters
I ran across a statement that seems exciting to me as someone that has written a lot of code in their career. It said: "Many of the "modern" software practices of the last decade were early adaptations to this shift, even if we didn't articulate them that way. Immutable infrastructure. Stateless services. Containers. Blue-green deployments. Infrastructure as code. These ideas all share a common premise: never fix a running thing. Replace it." These are a few sentences in this piece on . That's how a lot of software developers have viewed the world during the last decade and we've seen a lot of software advances in that time. The very successful developers and teams, who often speak at conferences and publish papers have adopted many of these practices. Serverless, containers, lots of tests allowing continuous deployment of new objects into complex environments that scale to levels many of us never thought possible. These are the very high performances talked about in the State of DevOps report every year. Read the rest of
/episode/index/show/voiceofthedba/id/41399155
info_outline
Over of Under Provisioned
06/02/2026
Over of Under Provisioned
Lots of people move to the cloud; it's common. In fact, it's very common to hear customers who are being asked to migrate their workloads to a cloud vendor for a variety of reasons. You might not agree, but often there is some reason to move to the cloud. Sometimes it's even moving from one cloud to another, just because one of the big three (AWS, Azure, GCP) seems more attractive this year than the one from last year. When you move, do you size your system for the peak? 80% of the peak? Perhaps there is another goal for which you design. Do you worry about ever being under-provisioned and letting customers have a slower system? Or do you ensure you never hit the peak, which increases costs? Read the rest of
/episode/index/show/voiceofthedba/id/41337920
info_outline
The New Software Team
05/21/2026
The New Software Team
One of the things I used to emphasize in talks about DevOps is that no modern software of any significance is built by one person. Everything takes a team, so the foundation of version control becomes extremely important. We need a way to coordinate work across multiple individuals and communicate what changes are being made. This requires a strong foundation, and that starts with version control. In 2026, that hasn't changed, but what has changed is the makeup of the team. No longer do I need a bunch of humans. In today's world, with extremely powerful AI LLMs, we can have a team of AI agents that write code, often at a pace far exceeding that of human teams. However, they still need to coordinate and communicate and ensure their changes mesh together. Read the rest of
/episode/index/show/voiceofthedba/id/41337575
info_outline
Limit the Blast Radius
05/19/2026
Limit the Blast Radius
You still need DBAs (that know how to back up systems and test restores). If you think you don't, or if you manager does, then perhaps they ought to read . This wasn't the case of an agent just running around with sysadmin access to all resources, or a lack of tests that allowed bad code to flow through a CI/CD process. This was a system design that had a hole in it. An API call to change infrastructure that could change both staging and production. Not something an AI set up, but humans did. A hole from both and the API vendor that allowed the AI agent to make the same type of mistake we've seen humans make. A mistake of not double checking, not verifying, not following the rules of getting a second set of eyes, even a second set of virtual eyes, on the code that could drop resources. Read the rest of
/episode/index/show/voiceofthedba/id/41121615
info_outline
What Can AI Really Do?
05/17/2026
What Can AI Really Do?
I wonder how many of you have tried vibe coding something with an AI tool. If you haven't, I certainly recommend it. I've been a bit amazed with a few of , including my . To be clear, there's plenty of vibe coding that might not be production-ready, but have you ever been handed code from a human developer you didn't think was production-ready? Or deployed code like that? Certainly, AI could exacerbate the situation, but it can also spark ideas, ease (and speed) development in small ways, and tackle the backlog of things your org needs. Especially small tools. Read the rest of
/episode/index/show/voiceofthedba/id/41120860
info_outline
There's Too Much to Learn
05/07/2026
There's Too Much to Learn
I remember getting started on SQL Server and trying to upskill myself in the mid-1990s. At that time, my employer was running a SQL Server 4.2 instance for a third-party application, but we wanted to rewrite our internal bespoke sales app to run on SQL Server. We were upgrading from Foxpro to Visual Foxpro and looking to move from shared dbf files to a SQL Server. There was a new release of SQL Server 6.5 during our development, and I wanted to learn more about it. I purchased and read the entire thing, getting prepared to finish development and then manage a new platform in production. I had updated copies of that book as SQL Server released new versions until SQL Server 2005. When that came out, there weren't one, but rather 4 books to cover the Inside SQL Server details (, , , and ). A similar thing happened with the , which grew in size to over 1400 pages for the 2012 version. It was a backache in a book if you put it in with your laptop. Read the rest of
/episode/index/show/voiceofthedba/id/41120780
info_outline
The Dangers of Dependencies
05/05/2026
The Dangers of Dependencies
Many of us working with databases know the problems of a single point of failure. We build HA/DR technologies into a lot of systems precisely because many of us know if the database goes down, a lot of stuff goes down. Broken software is easier to fix and rollback, but a broken database can be a much bigger problems. We also know an overloaded server doesn't handle a workload well, hence our quest for well-written SQL code, but we often lose that battle with developers. Read the rest of
/episode/index/show/voiceofthedba/id/41120640
info_outline
Who is Using CAGs?
05/03/2026
Who is Using CAGs?
While talking to a customer a few weeks ago, they mentioned that they used (CAG) everywhere. They also said they were amazing and wondered why everyone wasn't using them in other environments. Of course, I questioned the "everywhere", which turned out to be more of a default for new systems than a standard across all systems. That's likely true of most things since it's rare we get to update/patch/set something across an environment of any size and ensure every system is the same. Still, setting a CAG as a default makes some sense for enterprises. This ensures that in an HA situation I have my logins, jobs, etc. already on a secondary node. That's been one of the challenges of using lightly linked systems that only sync up database level information. Log shipping, Replication, Availability Groups can all work to keep a secondary ready to take over, but they all miss information that is stored in master or msdb. Read the rest of
/episode/index/show/voiceofthedba/id/41036410
info_outline
A Tool is Better than a Script
04/30/2026
A Tool is Better than a Script
While working with a customer recently, I heard this sentence: a tool is better than a script. The reference was that this customer preferred a known, tested, approved tool for most of their staff rather than a script built, lightly tested, and perhaps changeable by anyone in their organization. I was surprised, because in many ways, I've depended way more on scripts, more often, than "tools" in my career. Often I struggled to find tools that actually worked in the way I wanted them to and built them myself with Unix shell utilities, VB Script, PowerShell, or some combination of those or other technologies. Read the rest of
/episode/index/show/voiceofthedba/id/41036140
info_outline
Half of All Engineers
04/28/2026
Half of All Engineers
The AI LLM boom seems to show no sign of slowing down. Each time I think we've reached some level of crazy use or predictions, things take another turn. I still find myself pinging back and forth between this will be amazingly good and horrifyingly bad. Sometimes on the same day. Read the rest of
/episode/index/show/voiceofthedba/id/40880415
info_outline
Local Agents
04/23/2026
Local Agents
Recently I saw , saying that someone could build a general purpose coding agent in 131 lines of Python code. That's a neat idea, though I'm not sure that this is better than just using Claude Code, especially as the agent still uses the online version of the Claude model from Anthropic to generate code or perform other tasks. There's a video in the article showing how this code can be used to perform some quick tasks on a computer. However, the code isn't specific to Anthropic. It can be used with any LLM, and I started doing just that, with a copy of the code from the article, but modified to use a local AI LLM running under Ollama. You can see and feel free to download and play with it. It's expecting a local LLM on 11434. Read the rest of
/episode/index/show/voiceofthedba/id/40880330
info_outline
Every Database Has Problems
04/21/2026
Every Database Has Problems
Every database platform has some strengths and weaknesses. Some more than others. I caught from , and it made my day. I was having a tough one when this site got me to smile and chuckle out loud a few times. I especially like the MySQL and SQL Lite links (again NSFW). Every platform that you might choose to use to back an application can work in many situations. Certainly scale and load are factors to consider, but for the major relational database platforms, most will work fine for many applications. Some might work better than others, but there are always tradeoffs. There are pros and cons. This is also true for the major NoSQL platforms, though most of my experience is with relational ones, so I tend to lean in that direction. At the same time, any platform can fail horribly. Read the rest of
/episode/index/show/voiceofthedba/id/40879975
info_outline
The New OS Wars
04/19/2026
The New OS Wars
In the last year I've seen a lot of statements about data and sovereignty between countries. While there have been concerns in the past, there seems to be more worry around the world with AI services primarily being run by, and hosted by, US companies. Plenty of my customers at have concerns over our ability to see data when we run AI models, though we don't store the data. Once the session ends, Recently I saw a piece about , specifically the Windows OS from Microsoft. They are looking to move to their own version of Linux, as well as a number of open source software packages. This quote was fascinating to me: "We can no longer accept that our data, our infrastructure, and our strategic decisions depend on solutions whose rules, pricing, evolution, and risks we do not control." Read the rest of
/episode/index/show/voiceofthedba/id/40879850
info_outline
Working Better Under Pressure
04/16/2026
Working Better Under Pressure
One of my colleagues wrote , about how a DBA's pushback on bad code isn't to be difficult, it's because they can see the future. I never thought of myself as a modern-day , predicting the future of system performance. Apparently I had another title besides DBA. Working under pressure and with short deadlines often leads to short cuts. I've made them. I've implemented quick hot fixes. I've forgotten to port changes back to development databases. I've increased our tech debt load, just to solve a more immediate problem. Read the rest of
/episode/index/show/voiceofthedba/id/40807330
info_outline
Who is Irresponsible?
04/14/2026
Who is Irresponsible?
There was about an engineer using Claude and ChatGPT to build a feature. I am not sure how true these posts are or if they are designed to just create engagement, but it's still an interesting topic. The part that makes me think is that (supposedly) the engineer was fired because their "data" (code) was sent to American servers. The code was then deleted and the feature will be built without AI. First, read some of the responses before you form an opinion. There are some funny ones in there. There are a few I think are overblown and silly, and I skim past them. Someone is always more upset than I am, and more than I think they rationally should be, so I tend to let their outrage flow by me. Read the rest of
/episode/index/show/voiceofthedba/id/40807205
info_outline
Poor Names
04/12/2026
Poor Names
It's always interesting to me when I give product feedback to engineers at Redgate on their demos. Quite often they've built a feature that uses AdventureWorks or Pagila (PostgreSQL) or some other well known schema to evaluate how their particular thing works with a database. I try to remind them that many databases aren't well modeled and designed with consistent naming. I ran across that isn't showcasing databases, but it does show some poor naming in data being stored in a PDF. The developer who had to automate a process had to map these fields to database fields, which also might not be named very clearly. In fact, I think I've seen a few database models that used column names like the field names in the PDF. Read the rest of
/episode/index/show/voiceofthedba/id/40778805
info_outline
Acting with Confidence
04/09/2026
Acting with Confidence
Recently, I saw a graph about making decisions that showed the impact of both reversibility and consequences. and how one might approach decisions. If things are easily reversible or have a low consequence, we tend to make a decision and move on. Or we are willing to make a decision. One of the examples of such a decision was choosing what to wear out to dinner. It's easy to change, and (in general) of little consequence. Choosing to send a large amount of money to someone through Venmo (or some other mechanism), can be hard to reverse and have substantial consequences. This made me think of some of the DBA and developer decisions I've made in the past. When we work with databases, the changes we make can have a large impact and be quite consequential to our organization. Downtime, data quality, etc. could all impact revenue, profit, reputation, or even future prospects of survival. That can be a lot of pressure when you are deciding to refactor a data model or adjust a lot of data during a deployment. Read the rest of
/episode/index/show/voiceofthedba/id/40716855
info_outline
Barely Reviewed Code
04/07/2026
Barely Reviewed Code
Years ago I was giving a talk on software development and asked the audience how long it takes to review a PR that has 10 lines changed. Answers were in the minutes to tens of minutes range. I then asked how long it takes to review a PR that has 1,000 lines changed. Some people said hours, but a few people said seconds. I've often taken the latter, pessimistic view. Not because I don't think engineers want to do a good job, but because I know human behavior. Most humans will get bored, lose focus, and end up skimming through a large amount of code. Many (most?) people don't want to spend all that time, after all they have they their own code to write. They'll just approve the PR and assume testing will catch any major issues. Read the rest of
/episode/index/show/voiceofthedba/id/40622670
info_outline
AI Database Central
03/31/2026
AI Database Central
SQL Server Central has been a great success over the last 25 years. We've helped a lot of people improve their careers with the Microsoft Data Platform, primarily SQL Server, but we've published articles on other aspects of databases, including other platforms. I last month, with a few stories in various pieces. We even got Brian Knight to contribute a piece on . Over the years, we experimented with trying to get an SSIS Central or a SSRS Central off the ground. However, we struggled to find other people who would have been willing to partner with us to provide content and answer questions. Eventually, we gave up, though I wish today we'd have pushed forward with a PostgreSQL Central site a few years back. Read the rest of
/episode/index/show/voiceofthedba/id/40622525
info_outline
Prompt Requests
03/29/2026
Prompt Requests
One of the challenges of AI-assisted coding agents is that they tend to produce A LOT of code. Even in refactoring or migration changes, the AIs can work quickly and generate such a volume of code that the process starts to become overwhelming. For pull requests, for CI/CD build systems, and certainly for human reviewers, they can be overwhelmed. This can become a real problem with OSS projects, where submissions can grow exponentially to the point that maintainers stop looking at pull requests. I suspect the same thing might happen in corporate repositories when lots of developers can refactor or submit huge amounts of code produced by AI agents in a fraction of the time it took a year ago. I was listening to an interview with an experienced software developer and OSS project maintainer who said that he preferred getting a "prompt request" that contained a description of a problem and the specification for a solution that he could submit to his own LLM to get the code. Rather than use an AI to review a code in a PR written by a human or AI agent, a great prompt that can communicates the problem and solution is preferred. Read the rest of
/episode/index/show/voiceofthedba/id/40612020
info_outline
Is Your Time "Free"?
03/26/2026
Is Your Time "Free"?
We do a lot of research at , often contacting customers or and asking questions, getting feedback, listening to their challenges or criticisms. We take that information and it helps guide us to build the tools that help you in your job. Recently I watched a call with a customer that uses our famous in their job and has for years. In this case, the call was about the value of and how that might fit in their organization. The person performed a lot of manual work to deploy code changes, and could see the way in which Flyway helps, but wasn't interested in saving time. They saw their time as free. I assume their employer felt that way as well. Read the rest of
/episode/index/show/voiceofthedba/id/40597885