There's Too Much to Learn
Voice of the DBA
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...
info_outline
The Dangers of Dependencies
Voice of the DBA
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
info_outline
Who is Using CAGs?
Voice of the DBA
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...
info_outline
A Tool is Better than a Script
Voice of the DBA
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...
info_outline
Half of All Engineers
Voice of the DBA
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
info_outline
Local Agents
Voice of the DBA
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...
info_outline
Every Database Has Problems
Voice of the DBA
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....
info_outline
The New OS Wars
Voice of the DBA
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...
info_outline
Working Better Under Pressure
Voice of the DBA
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
info_outline
Who is Irresponsible?
Voice of the DBA
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...
info_outlineFor much of my career as a younger person, I was mostly concerned with salary at a job, along with the opportunities for my career. I really wanted to know how much money would hit my bank account and cared most about that. I also wanted to know if I would learn something or get a better title or work with a technology that might help me in the future. That drove me through quite a few jobs in my 20s and 30s, leaving some for more money and more opportunity.
As I got a family, I became more concerned about healthcare since that industry is a mess in the US. Often when I looked at a job, I perused other benefits but didn't give them much weight, mostly concerned with salary and the cost of medical insurance. I also somewhat cared about who I worked with (the team), but that was more for helping me choose between different jobs. It wasn't something I thought of as a reward, though I should have.
Read the rest of Knowing Your Total Reward