Voice of the DBA

Part of my Redgate work is with customers who need to monitor their database servers. With estates growing quickly, both in scale and types of database platforms used, keeping an eye on everything can be challenging. Add in the lack of staff growing as quickly are the number of servers, and I find many companies seeking out monitoring tools to better help them manage the entire estate.. When someone evaluates a tool, one of the first questions from many people is about load. They are concerned about the load a tool puts on the system, which is always some amount. Most tools say they use less than 2% of total resources, some might hedge at 5%. Hopefully, there's no more impact than 5%, though that might seem to high, especially if you have a busy database server already. Read the rest of Multiple Monitoring Tools

Are you looking forward to SQL Server 2025? Or perhaps you think this is just another release, or perhaps you are not looking for new features or capabilities in your environment. Maybe you don't care about new things, but are looking for enhancements to features introduced in 2017/2019/2022. There is certainly no shortage of things that can be improved from previous versions (cough graph *cough). I ran across an article on the five things that one person is looking forward to in SQL Server 2025. It's a good list, and the things included make me consider an upgrade. Certainly, any improvements in the performance area, especially with all the investments made in Intelligent Query Processing over the last few versions, are worth evaluating. They might help your workload, or they might not, but if they do, then upgrade. Read the rest of SQL Server 2025 Excitement

I had to make a few changes to a SQL Saturday event recently. The repo is public, and some of the organizers submit PRs for their changes, and others send me an email/message/text/etc. for a change. In this case, an organizer just asked for a couple of image updates to their site. I opened VS Code, created a branch, added a URL for the images, and submitted my own PR. After the build, I deployed it. And it didn't work. Read the rest of Patching the Patch

When talking about DevOps, the goal is to produce better software over time. Both better quality as well as a smoother process of getting bits to your clients. There are a number of metrics typically used to measure how well a software team is performing, and one of the things is Change fail percentage. This is the percentage of deployments that causes a failure in production, which means a hotfix or rollback is needed. Essentially we need to fail forward or roll back to get things working. For most people, a failed deployment means downtime. I've caused a service to be down (or a page or an app) because of a code change I made. This includes the database, as a schema change could cause the application to fail. Maybe we've renamed something (always a bad idea) and the app hasn't updated. Maybe we added a new column to a table and some other code has an insert statement without a column list that won't run. There are any number of database changes that might require a hotfix or rollback and could be considered a failure. Read the rest of What is a Failed Deployment?

Many of us are faced with choices and decisions constantly in our jobs. How do we approach a problem? What should we do as a team to get the work done? How do we code or manage or test or do something else with a database? Maybe more importantly, how long do we spend deciding? Read the rest of Shorten the Debate

At an event recently, I had a chat with someone after one of my sessions. I had been speaking on DevOps and ways to better structure your team and build software. After the session, one person asked me if I'd read The Mythical Man Month and if I felt we'd gotten a lot better at building software since that book was published. I do think we have gotten better, way better, in fact. I caught another review of the book a while back from the Pragmatic Engineer. That view looked at what's changed in 50 years since the first edition, as well as contrasting the world today. You have to subscribe to read that one, but I'll give you a few thoughts from me on the book itself and the review. Read the rest of Reflecting on the Mythical Man Month

I've been reading an interesting book that looks at some of the ways that we can better build software in enterprises. One of the side notes in the book is that the tech companies have the funding and the ability to disrupt many other types of businesses, not just technology. Google, Amazon, Microsoft, and others have delved into other types of industries, potentially pushing others out. We see Amazon becoming as much a shipping and logistics company as they are a retailer. There was a unionization vote, which passed in 2022. Recently, another one failed. Amazon continues to fight these efforts, trying to prevent workers from collectively negotiating the terms of their employment. Read the rest of IT Unionization

At a recent event, I had a student ask about how to get started as a data professional. What types of things should they do? What platform should they work on or learn? Where should they focus time? What tools are available? Those are all good questions and many of you likely have your own advice. I'll give a few things to think about today, which are good for anyone that might want to get into the data field. I think this is still one of the better technical careers. I've suggested this to my kids, though only one of them went into a technical area. One is a therapist for autistic children and one helps run the ranch while pursuing a graduate degree in literature. Read the rest of Helping Students with a Data Professional Career

I saw an article on AI usage that is based on an upcoming book that suggests redesigning the world around new tech, not adding it to existing things. The first example is how electricity was introduced to existing factories, but it only provided some incremental gains until new factories were redesigned around electric motors. There's also an example given about reworking hotels to remove the front desk since that feature isn't needed. Instead, people could walk in, and an employee with a tablet could find them to check them in. I'm all for rethinking and redesigning processes. I do think we have a huge glut of software in many organizations that exists because processes have evolved across time, but not everything and we keep our old software. When we have a new need or want a new capability, we add new software (or add features), but we don't necessarily throw out all the old software, processes, or habits. That wouldn't be practical, often because when we implement something new, it might not meet all our needs. Or at least we don't know it meets our needs at first. Read the rest of Changing the Paradigm of Work

As a part of my job, I often work with customers on how they can get database code into a version control system. That's Git for the most part today, which is the most popular system in the world. I'm comfortable using Git for many basic tasks, but I am not an expert by any means. I've used version control for years, and quite a few systems, and I like Git as a way of managing code. I have been surprised how many people aren't comfortable with version control or Git. Many don't have the habit, but are amenable to it. What I'm amazed by in 2025 is how many people don't use it, given that so many tools we use to work with databases, and even other systems, will store items in Git. This isn't just for development code, but also for infrastructure code. Lots of data tools and servers can store data in Git and use it to deploy changes to all kinds of systems. I'd have expected more people to know Git. Read the rest of Does Version Control Scare You

It likely isn't a surprise to many of you that executives like AI. A survey shows that 74% of executives surveyed have greater confidence in AI-generated insights than advice from colleagues or friends. At the board level, even more (85%) favor AI-driven advice. That's amazing to me, and while I might think this is a bit too much trust being placed in these GenAI LLMs, perhaps it's also partially because they work with too many people who aren't great at their jobs. Plenty of people skim through data or focus on certain things and might miss the details. While an AI can read and summarize a lot, it might not have the context we expect. I tend to be a bit skeptical of AI summaries, often because they don't necessarily weigh the different parts of an article the same way that I do. Read the rest of The AI View From Above

I read a piece recently that got me thinking that data breaches might be inevitable. Disclosure: This was written by Redgate, for whom I work, titled "Data breaches May Be Inevitable—Compliance Failures Don't Have to Be". It's based on our research with the State of Database Landscape survey as well as feedback and conversations with customers. The thing that caught my eye was the first part: data breaches may be inevitable. Do you think that's true? Are we doomed to lose data in our organizations, not as a possibility, but something that will happen at some unknown time in the future? Those of you who have suffered breaches might agree with this, but for those of you who haven't had to deal with that situation, are you resigned to it happening at some point? Read the rest of Are Data Breaches Inevitable?

Who among us has deleted a production database? I'd hope it's very few of you that have done this in your career. I'm sure a few of you have deleted (or truncated or updated all rows for) a table in production. I've done that a few times, but fortunately, I've been able to recover the data quickly. I had this happen in SQL 6.5 and was grateful I could start a single-table restore before my phone rang. Read the rest of Deleting a Database

The DORA organization is constantly researching how to better produce software at any organization. This is similar to work done by Carnegie Mellon Software Engineering Institute many years ago. Both groups are trying to determine what things help engineers work better and produce high-quality software. On the DORA site, there is a database change management page, where they recommend approaches to managing database schemas. The main thing they talk about is treating all schema changes as migrations, which is something some people do. However, many teams also like a desired-state-configuration approach, where they just deploy all the changes from dev (or QA) to prod in a state-based flow. Both can work, but I do think as software matures (and becomes legacy), migrations are preferred. The article lists lots of frameworks in different languages. Flyway is among them, which is the product on which I work and sell at Redgate. If you haven't looked at a migrations framework, I'd recommend you do so. They do really give you a tremendous amount of control and flexibility. There are trade-offs, so I'm not blindly recommending this approach, but it's worth educating yourself on how migrations frameworks work. Read the rest of Database DevOps Recommendations

I'm sure many of you have tried a GenAI LLM to do something. Maybe write some code, maybe get some sort of recommendation or suggestion, maybe to rewrite something or summarize text. I'm sure you have had some feelings about whether the tool made you more or less productive. There was a trial conducted by the Australia Department of the Treasury on Microsoft's 365 Copilot, asking for volunteers to participate and use the tool in their daily work. They used it and then completed a survey, which are summarized in this piece. Only 218 people went through the trial, and the results are interesting. Read the rest of How Helpful is a GenAI Copilot

Certifications can pay off, at least in some areas. There's a piece that talks about pay rising for some tech professionals when they have some credentials. Networking, architecture, and project management are mentioned in the report, as are database and data management. I haven't seen the source report, and I'm not sure which certifications are getting higher pay rises, but I'd guess that newer data technologies, things related to cloud databases, and even anything related to AI is likely to get you a raise. Read the rest of Rising Pay for Certifications

I thought this story about a programmer and a GenAI to be rather humorous. The individual was a game programmer and used the Cursor AI assistant to help them generate some code for a game. After a few hundred lines of code, the AI delivered this: "I cannot generate code for you, as that would be completing your work. The code appears to be handling skid mark fade effects in a racing game, but you should develop the logic yourself. This ensures you understand the system and can maintain it properly." That response makes me actually smile to myself and chuckle out loud. I likely wouldn't feel the same way if I were asking for help with some code to handle a task like this, but it's kind of funny to have the GenAI stop and say this. However, it's akin to the RTFM response plenty of humans have given others when they were asked a question. This is pointed out in the article as the type of response plenty of people see on sites like Stack Overflow. Fortunately, I think we've avoided a lot of that response on SQL Server Central. Read the rest of Learn to Code

When is the last time you interviewed for a new position? It could have been at a new company, or maybe you had an interview was for a different position inside your existing company. Perhaps you needed to talk to a manager internally for a new project. I've tried to treat all my one-on-one meetings or reviews as interviews since I'm usually trying to impress someone enough to get a raise or promotion. Preparing for something you do rarely is hard. Most of us have interviews very infrequently, and we often aren't prepared to impress others. If your partner or a close friend is also a business person, perhaps they can help you get ready, but I've found that most people struggle to help others prepare as they don't know how themselves. Read the rest of Interview Tips

I heard Brent Ozar recently talked a bit about the SQL Server platform and its future. He also mentioned that Fabric has distracted the data platform team and it isn't a great product. I tend to agree, and I see too many bugs, holes, and problems. However at the end of this short snippet, he talks about SQL Server with an interesting comment. Is SQL Server feature complete? Read the rest of Is SQL Server Feature Complete?

I get the Gates Notes email periodically and I always find it interesting to read. Like Bill Gates or not, he is a very smart individual and has thoughtful things to say. Even when I don't always agree with him, I enjoy hearing his view and have enjoyed seeing him deliver presentations. In fact, one of my career highlights was at SQL Saturday #175 - Fargo, held at the MS campus. Bill Gates was speaking to employees that day and we were allowed to watch the Q&A from the balcony. Later, I saw him start to leave and stop by a sign. He asked someone about SQL Saturday. When they explained the idea for free conferences, he said "that's cool." One of the recent emails talked about the 50th anniversary of Microsoft, with the original source code available for a BASIC interpreter. It's an interesting read to me, since I learned BASIC first (and a little assembler) on an Apple II and a TRS-80. I didn't start a company, but I certainly appreciate the excitement of tackling a programming challenge back then when memory and disk were in short supply. Most of my early programming tasks had me worried about how much memory and disk I was using, trying desperately to minimize both. Read the rest of 50 Years of Microsoft

At the end of last year, I ran into a friend I hadn't seen in a long time. We were chatting and this person mentioned that they were looking for a new job. They had been laid off and needed something. This is someone with a lot of experience and skill, so I wasn't worried for their career or future. At the time, they mentioned they had gotten an introduction and interest from Amazon, but they weren't interested in a position because of the return-to-the-office (RTO) mandate that Amazon was implementing. I was recently chatting with another friend at a different company. This person manages a tech team, and was looking to hire another data engineer, but was told they could only hire in a certain city (City A)  in the US. In this case, it was the city with their main office. They have offices in a few cities, and a large one in City B, but the organization has been thinking of their own RTO plans and has limited hiring. My friend is now wondering if they need to consider moving to City A (not likely) or find a new job. They don't want to have to go to the office every day in City B. Read the rest of The Return to the Office Debate

The revolution with GenAI has been quite the ride since 2023 and quite a few people have been concerned that their employment status might be in jeopardy. I can certainly understand that, especially in light of the tight budgets, widespread layoffs, and executive views on AI technologies. There was an article recently talking about AI taking over some jobs with a few tips on how to stay employed. While tech workers weren't mentioned as being vulnerable, repetitive data-heavy jobs, such as data entry clerks, telemarketers, and cashiers were. That last one is interesting. Lots of companies have tried to use automated checkout stations, but this hasn't necessarily eliminated cashiers. Maybe there are fewer, but lots of companies in the US have rolled back some of these efforts as fraud, mistakes, and slower checkouts have been an issue. Read the rest of Staying Employed

One of the challenges in software development is coordinating database and application changes when one depends on the other. I find many software development teams struggle with this, especially in today's environments when no one wants to take a system offline. While some companies can stage and manage deployments, many of us find our systems need to keep running 24x7 with minimal outages (if any). Lots of you work in environments where your software is changing on a regular basis. Plenty of you will either be developing those changes, or managing the systems to which those changes are deployed. You likely will be coordinating with other people (in either case) to deploy a software artifact (C#, Java, Python, etc.) and a set of database changes in order for your clients to use whatever new functionality is being delivered. Read the rest of Database First or Application First

I saw an article recently that a quarter of the Y Combinator startups have 95% of the code in their repos being AI generated. The article notes that if no other startups had any AI generated code (no idea the likelihood here, then about 24% of their code for startups is GenAI written. 24% Is that high or low? If you think about all the code you've written in the last year, how much of it could be reasonably generated by AI? All the queries, schema changes, test code, dummy data insertions, refactoring to add a column to a table or result set. Could it be AI written?   Read the rest of How Much AI Code Would You Use?

Some of you reading this are database administrators (DBAs) who manage systems as their full-time job. Others of you might be developers, analytics people, or someone else who has another job, but you get stuck with managing the database somehow. I've seen a receptionist and a dental hygienist act in this role. We may call you the accidental DBAs, though that doesn't imply you are good or bad at managing databases. I got into this line of work as an accidental DBA who was also a developer.  No matter what your job title, my guess is that you aren't over-staffed at your organization. Likely you wish you had one (or more) more person to help keep up with the work. It seems that we never have enough time to get everything done in a week. And that's with a full staff. What do you do when someone is sick or goes on vacation? If you're like me, you get further behind and feel extra stress while your coworker is out of the office. Read the rest of Part-Time DBAs

The use of feature flags in software development has become more and more prevalent over time, especially as teams move to DevOps-style development with frequent releases. I've often thought that using feature flags allows technical people to separate out the deployment of some feature or change from the release of that to users. There are a number of articles on this style of work (feature flag driven development, Why Use Feature Flags?) as well as a discussion at Reddit. I am a big believer in feature flags helping with improving your software in many ways. These articles (and others) highlight the advantages that a software organization gains by using feature flags. Failed releases become less of an issue, as the specific change that doesn't work can be turned off. This can even work with databases. I can deploy a database change and at a later time have the code (or new table/column) start being used when a feature flag is set. If there is an issue, I can turn off the feature flag and stop using the code (or populating the schema). I can then clean things up, even saving data before I make a change. Read the rest of Using Feature Flags

A domain is a set of possible values (among other definitions). I use this word a lot in my work, often with a problem domain (the thing you're trying to solve) or the domain of possible values (like the US States and Territories list). That last one is interesting, as this is often the set of data we stick in some reference or lookup table to use in a form on a screen. There is a domain as part of the SQL specification, which I never knew about. I was reading an article from Joe Celko on the CREATE DOMAIN statement. This doesn't exist in SQL Server and T-SQL, but it has been a part of PostgreSQL for quite a few versions. The article talks about the definition of a domain from a few very experienced database design people. Read the rest of A Domain for Data

The DORA organization is dedicated to helping others build software better and faster, at a higher quality, and in a way that is more efficient. They continue to compile and publish the Accelerate State of DevOps report every year, which is a fascinating read. As a part of the report, they have identified four key metrics that identify high performing organizations in terms of software. These are divided into two areas: throughput and stability. Throughput measures are change lead time and deployment frequency. Stability measures are the change fail percentage and failed deployment recovery time. Read the rest of Database DevOps Metrics

If you're a fan, no. You're chomping at the bit, waiting to get everyone using GenAI models in their work. If you're skeptical, then you might think it's never coming to take your job, be a personal assistant, help you with coding, etc. Pick the task it won't help you with. A more nuanced view, which is similar to mine, is from Kendra Little, in which she says AI will eliminate DBA Jobs  Faster Than You Think, I'm not quite as pro-AI as Kendra, mostly because I see so many companies that are slow to change, slow to adopt new tech, slow to adjust their thinking. They just soldier on and keep running their business, as they've been doing for decades. Even when you might make a case for change, or prove it's worthwhile, they just don't spend the time to change. Read the rest of Is GenAI Coming Faster Than You Think?

Well, not really the end. I doubt anyone running SQL Server 2019 is going to stop (or upgrade) just because mainstream support ended. Actually, I wonder how many of you know that SQL Server 2019 passed out of mainstream support on Feb 28, 2025. I do think the 6 or 7 of you running Big Data Clusters likely knew this was the end of any support. I saw a report in the Register on this, which includes a survey of which versions are still running. This is from an IT asset firm and matches Brent Ozar's Population report. 44% of you are running SQL Server 2019, which is the largest percentage. Since there's an additional 32% of you running versions older than 2019, I'm sure that upgrading isn't a priority. Read the rest of The End of SQL Server 2019

It's no surprise that our systems are under attack by all sorts of criminals. Some organized, some opportunistic, some just aiming for vandalism. We need to protect our digital systems to prevent issues, and a part of better protection is reducing the number of places that are vulnerable. Those places include databases. This article discusses the rising costs of data breaches and the increased frequency of attacks. It also examines the increasing number of regulations that are demanding proof of stricter security measures. It can be hard enough to defend production systems, let alone protecting dev/test environments. I see an increasing number of organizations that limit access to production systems, even to the point that this impedes some of the daily work habits of technology professionals, but that is probably a good thing. Too many of us are too lax when it comes to security. Read the rest of Lower Your Attack Surface Area

This is a strange time for many technology professionals and their employment. It seems many organizations have open positions and are struggling to fill those slots with qualified candidates (one look at this). At the same time, many other organizations have followed the large technology firms (FAANG, MSFT) and laid off large numbers of their staff in the last year. At the same time, with the hype and rapid growth of GenAI systems, we have companies that are looking to machines to fill some of their labor needs. Salesforce noted that they did not expect to hire more software engineers in 2025 as their plan was to use AI tech to help them write enough code. They've seen productivity gains with AI tech, so they aren't adding more developers. They still need human developers, just not more of them. Read the rest of The Job Outlook for Database Professionals

Recently there was some online complaints about social security numbers (SSNs) in the US being duplicated and re-used by individuals. This is really political gamesmanship, so ignore the political part. Just know that social security numbers appear to be one of the contenders used in many data models. I found a good piece about how SSNs aren't unique, and have a mess of problems. Despite this, many people seem to want to use SSNs as a primary or alternate key in their database systems. They also aren't well secured in many systems, even though we should consider this sensitive PII data. Read the rest of A Poor Data Model

I've been working with databases for a long time and there are no shortage of things I've seen other people do that I don't like. Sometimes I shake my head a little. Sometimes I might groan inwardly (hopefully not aloud), and sometimes I might make an effort to convince someone else to do something differently. Sometimes I'm really annoyed (or angry) and don't even know what to do. Read the rest of Your Biggest Data Model Complaints

Erin Stellato, a program manager at Microsoft, asked a very interesting question on LinkedIn: "why do you *not* want a Copilot in SSMS?" That got me to stop and think a minute. Why don't we want to use an AI to help us? It's a good question, given the hype and (maybe) potential of the technology. While it might not help you now, or with your specific thing, it might help others, so are there good reasons not to use AI technologies, like the GenAI LLMs? Read the rest of Why Not Use AI?

I caught an article on AI skepticism and there was a point in the article where trust was mentioned. Specifically the reasons that people distrust an AI or tech tool is that it makes a mistake, so they stop using it. A few examples of this were using a writing AI that made a grammar mistake or a GPS routing device that added a wrong detour. In those cases the humans stopped using the assistance of the algorithm because they felt it wasn't trustworthy. What's fascinating to me is that I had this same conversation with a human the day before. Someone mentioned they were working with a group and they misstated something. After that, the group stopped listening to all this person's advice, thinking it was all suspect. Essentially one mistake overrides everything else. Read the rest of Trust is a Funny Thing

I don't know how many of you will be disappointed or impacted by this, but Azure Data Studio (ADS) is being retired, as of 6 Feb, 2024. It will be supported for a little over a year, until 28 Feb, 2026. On one hand I'm not surprised, and on the other, I'm a little shocked by this. I have written a number of articles on ADS, and shown how things work, as well as pointed out a number of things that don't work well in the product or its extensions. These pieces have gotten a number of reads, and people have commented on them, so I wonder if there are a lot of you that are upset by this. Is this going to change the way you work? I will say that it will lightly change my work, as I do use ADS to connect to PostgreSQL, but not so much for SQL Server. Read the rest of The End of Azure Data Studio