Dear SQL DBA - Data Roles: DBA, DBRE, and Data Engineer
There are lots of jobs for data folks. In this episode, I discuss three hot job titles: Database Administrator (DBA), Database Reliability Engineer (DBRE), and Data Engineer (DE).
There are lots of jobs for data folks. In this episode, I discuss three hot job titles: Database Administrator (DBA), Database Reliability Engineer (DBRE), and Data Engineer (DE).
I recently posted on LinkedIn that I was interviewing for a SQL Server database administrator role for the first time in a long time. I invited folks: “Ask me your favorite interview question!”
Stephen Vakil had a great one: “when should you use SQL Server to store your data?”
For situations where SQL Server is already in use and there’s a relatively low barrier to entry, I think it’s simpler to turn this question around and ask, “When is SQL Server not a good choice for storing your data?”
This post is also available as a podcast episode, and on YouTube.
It’s Down Tools Week at Redgate.
In this episode, I share what “Down Tools Week” is, what I’m working on this week, and why I think it’s a terrific experience for fostering creativity, innovation, and teamwork. In closing I share some thoughts on variations of this kind of project which you might use in your own organization.
Many people use entrenched processes for database development that have been in place so long that it’s hard to imagine doing it any other way. In this episode, I share three things that should NOT be normal for database development– but which are incredibly common.
I’m not an expert on collation in SQL Server, but there are a few important facts which I’ve had to learn the hard way. In this episode I share the basics, along with helpful resources to learn more.
Learning Git can be daunting for DBAs. In this 20 minute episode, I discuss why learning a VCS is necessary for DBAs, then give three tips on scoping your project, choosing the right tools, and making sure the project is successful.
You’re a DBA, and your development team is all-in on doing DevOps, and they want to include the database. Should your DBA team limit the permissions or options for automation? Or should you instead re-think how your two teams work together?
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.