3 ms·
A lot of it depends on the particulars of your database system. But there are certainly tools/solutions that exist, and essentially they all boil down to the sa
by daigoba66 11y ago
A lot of it depends on the particulars of your database system. But there are certainly tools/solutions that exist, and essentially they all boil down to the same pattern: migration scripts should be executed exactly once in order. How this is done varies.
I do a lot in the .NET/SQL Server world, and my tool of choice is one that I wrote: http://josephdaigle.me/2016/04/03/introducing-horton.html http://josephdaigle.me/2016/04/03/introducing-horton.html. Conceptually, what this tool does could work for any RDBMS.
- junto 11y agoSimilar tools for the . NET world include Roundhouse and fluentmigrator.net. I'm personally more of a fan of the latter, but we use both in our company in conjunction with Octopus Deploy. Roundhouse needs a bit too much Powershell for my liking.
- briHass 11y agoOctopus Deploy also has a small tool, DBUp, which can run migration scripts. I've been using it for years with no issues. https://dbup.github.io/ https://dbup.github.io/