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.
on June 13, 2019
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, Kendra discusses DevOps team topologies, the changing role of DBA teams in DevOps, and the opportunities available in creating communities of practice around database development.
Prefer to listen on the go? You can get this episode on iTunes, download the audio file, or find Dear SQL DBA in your favorite podcast app.
Bookmarks of topics covered
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
Links from the video
DevOps Topologies - https://web.devopstopologies.com/
Communities of Practice - https://wenger-trayner.com/resources/what-is-a-community-of-practice