How to Stop SSDT / Database Projects / SQLPackage from Modifying Database Options
SQL Server’s free state-based version control tooling was introduced under the ‘Data Dude’ brand, then became known as ‘SQL …
Read MoreBy Kendra Little on • 1 min read
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?
In this 40 minute episode, I discuss DevOps team topologies, the changing role of DBA teams in DevOps, and the opportunities available in creating communities of practice around database development.
00:30 - Our question, from a DBA
7:00 - Why bother with DevOps?
9:23 - Team topologies, aka rethinking how the teams work together. This discussion includes notes on where and when DBAs review changes and talk about architecture in a DevOps way of working.
21:20 - Changing the DBA role from gatekeepers to internal consultants
32:30 - Creating a community of practice
38:38 - Recap and wrap up
DevOps Topologies - https://web.devopstopologies.com/
Communities of Practice - https://wenger-trayner.com/resources/what-is-a-community-of-practice
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.