Part-Time DBAs
Voice of the DBA
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....
info_outline
Using Feature Flags
Voice of the DBA
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 (, ) as well as . 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...
info_outline
A Domain for Data
Voice of the DBA
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 . 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...
info_outline
Database DevOps Metrics
Voice of the DBA
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 report every year, which is a fascinating read. As a part of the report, they have identified 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
info_outline
Is GenAI Coming Faster Than You Think?
Voice of the DBA
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 , 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...
info_outline
The Inefficiencies of Kubernetes
Voice of the DBA
info_outline
The End of SQL Server 2019
Voice of the DBA
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 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 on this, which includes a survey of which versions are still running. This is from an IT asset firm and matches . 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...
info_outline
Monoliths and Microservices
Voice of the DBA
info_outline
More Supply Chain Attacks
Voice of the DBA
info_outline
Lower Your Attack Surface Area
Voice of the DBA
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. 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...
info_outlineThe 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