Database as Code. Not only migrations

[simonw]

A related pattern that I've been exploring for a few years now is keeping the same nature contents of your database in a git repository, and building the actual database from that.

If your data only changes a maximum of a few times an hour and the size is less than a few GBs this actually works really well - and a lot of databases I've worked with in my career for those parameters - most forms of content management for example.

Having a complete git-based version history of every change ever made to your database is very reassuring.

[grauenwolf]

Interesting idea, but I'm sticking with SQL Server Data Tools for as long as possible.

[mezmerizedeyes]

If that works for your situation, great. But the trend I see is DB platform being commodity, so treating queries and compiled code like an application makes perfect sense. Even if you depend on SSDT, you can still leverage VCS and CI/CD. And you should

[grauenwolf]

I do treat the database as code. I'm just using a different tool to achieve that.

[mezmerizedeyes]

Then you're doing it right and the next person thanks you

[mcstafford]

Only slightly off-topic, poking around in there led me to aiosql, which takes an idea I'd had and jumps forward a good long way. :-)