This is the first in a series of posts about simple things that I had a hard time figuring out in Azure DevOps services.
It can be very useful to enable Continuous Integration for multiple folders in your DevOps pipeline: say, for every branch created under releases/ or features/. But configuring this can be strangely confusing!
Like a lot of developers and database administrators, I do a fair amount of short-term problem solving during the course of my normal work week.
Building your database code is an essential practice to ensure that it compiles from source and that dependencies are met. But things can get tricky when you have objects in some databases which is dependent upon objects in other databases: or even circular dependencies.
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?
I recently chatted with some folks who have a permissions problem in SQL Server. The permissions problem isn’t technical: it’s a process problem.
One of the cool things that I do as an Evangelist at Redgate is to periodically visit company headquarters in Cambridge.
The other Evangelists and I get to meet with every software developer, product manager, and UX designer at Redgate over a series of meetings. We talk about features that teams have released lately and what teams are looking at doing in the near future. We get to give feedback based on what we hear from the community and from folks in the sales process. We also get to share what we think teams should work on.
Today I got a bit closer to a meaningful definition of automation, as it applies to the software development process. I’ve been turning this concept over in my head for a while, which is partly related to the dreaded question of licensing.
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.