[MikeTV]

I've been dogfooding my own SQL Server Management Studio add-in, VersionSQL [0]

Priorities in its design and why I prefer to use it: It lives where I work, in SSMS. It's as close to zero-friction as possible, so I'm not getting slowed down or sitting around waiting on it when I could be working. It commits SQL code to a subfolder right alongside the application code in Git/SVN.

Cons: Skips some of the more complex features of other apps in the space, like building migration scripts for deployment or rollback of changes. Also, the add-in is maybe a bit too zero-friction -- it's nice that it doesn't get in my way, but that makes it easy to neglect committing code altogether. Have a couple rough ideas about how to solve that one (suggestions welcome!)

[0] https://www.versionsql.com/