Kevin Hill is looking out for tightwads like us:
Every DBA has been there. Trying to keep track of database schema changes while developers have their fancy Git repositories and version control workflows. Meanwhile, database changes are often handled through a mix of manual scripts, backups, and maybe a SharePoint folder full of “final_final_v2.sql” files.
Did you know that SQL Server already has a built-in tool that can help you track your database schema changes, without spending a dime on third-party tools?
I hadn’t thought about Kevin’s solution that way, but it does make a lot of sense as a way of quickly getting files into a source control repo.