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.
As a part of my charity work, I manage the SQL Saturday site, which is stored in a public GitHub repo and all changes are submitted through pull requests to make changes to the site. A few organizers will fork the repo and submit changes to me as pull requests. I love those as I can approve those on my phone. A very few organizers can merge their own changes, as they’ve built up trust. I am, however, surprised at how few people are willing to do any Git work.
It seems that so many data professionals don’t want to use or learn Git. I’d have thought this was a core skill for many technical people these days. At least the core ability to clone, branch, commit, and create pull requests. Squashing commits, rebasing, and more can be challenging, but often there will be someone in your organization that can help you if you need to perform those actions.
I wonder if you are intimidated by version control, or if you find yourself too busy to use it, or maybe you don’t think it’s valuable. I am curious what you think today.
I’ve written about how to use Git in ADS (don’t do that anymore), but those instructions work for VS Code. I’ve written a bit about how DBAs can start using Git. If you don’t like the CLI, there are many thick clients, which are easy to use. Give Git a try today and see how it might help you manage and version your code, your scripts, your documentation.
Steve Jones
Listen to the podcast at Libsyn, Spotify, or iTunes.
Note, podcasts are only available for a limited time online.
Voice of the DBA 
I find it alarming that in 2025 anyone is unwilling to embrace some form of version control with development even if it is very rudimentary and nothing as detailed as GIT. In my situation we are to small to warrant something elaborate as the only things we change that would need some form of version control are DB objects like SP’s, UDF’s, VIEWS and the files that make up custom reports we use (ie rpt for Crystal Reports, or rdlc for SSRS). I ALWAYS update th eversion anytime any change is made and not only do we version it but we include notes on when it was changed, why it was changed and who requested the change when applicable. This has saved my own butt a few times when a change was requested and made and then 6+ months later someone asks why X was changed and I can say because such and such asked me to. Without that I know I;d be blamed for making a change that should not have been made.
Without naming anyone or any company, I can tell you that this lack of version control has been a headache to deal with as I previously worked with a piece of software where the vendor did not have any real version control for the external files the software used. When there was an issue with something, usually a report, the fix was to have us (the client) reinstall all related files because support had no way of determining if the problem was that we were not using the latest versions or if it was something else like a problem in the source data.
EXAMPLE:
ME: Hello Support? Our Balance Sheet reports are showing out of balance.
SUPORT: OK , first let’s reinstall all your files to make sure you are on the right/latest versions. If that doesn’t work contact us again.
ME: Again?
Had they even a rudimentary form of version control they could have reduced a lot of unnecessary work on the clients as well as their own support people who also complained about this and was ignored by those in charge. Sometimes it was due to not having the right version and sometimes it wasn’t but we always had to do the above first because the vendor couldn’t be bothered with version control.
They did EVENTUALLY change that but only after years of clients (mainly my company) complaining and pushing for change going so far as having to effectively shame them publicly at an annual users conference the vendor held for clients.
LikeLike
I agree. It is alarming and maddening. I’m amazed at how many people find it hard, don’t put in effort, or are scared.
LikeLike
Pingback: Source Control: A Call to Action – Curated SQL