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!
Sometimes you keep a classic around.
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?
This post is a part of #tsql2sday, a monthly community ritual where a topic is proposed by a community member and everyone is invited to join in.
This month’s topic is from Mohammad Darab, who encouraged us to: “Write your 20 year old self a letter. If you could go back in time and give yourself advice, what would it be?”
The advice I would give to my 20 year old self is the same advice I give to myself today, more than 20 years later:
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.
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.