Git for DBAs: Series Contents

Git, explained in terms a DBA already knows.

A woman gardener grafts a green branch onto a navy tree whose branches hold small database cylinders.

Each post maps one Git concept to a database idea: a repository as a database, branches as database copies, merging as synchronization, push and pull as backup and restore over a network, stash as a temp table, rebase as ALTER TABLE on history, tags as named snapshots, and cherry-pick as a cross-database INSERT…SELECT. The last post brings it together for SSDT projects.

  1. Your Repository Is Just a Database
  2. Branches Are Just Database Copies You Can Merge Back
  3. Merging Is Like Synchronizing Two Databases
  4. Pull, Push, Fetch - It’s Just Backup and Restore Over a Network
  5. Stash Is Just a Temp Table for Your Changes
  6. Rebase Is ALTER TABLE on Your Commit History
  7. Tags Are Database Snapshots You Can Name
  8. Cherry-Pick Is Cross-Database INSERT…SELECT
  9. Git for SSDT Projects: Where It All Comes Together

Questions or corrections are welcome on Bluesky or LinkedIn. See all series on this blog.