4 ms·
Another options is liquibase[0]. I use the diff[1] tool to create a changeset and then convert it to sql before applying it to my db. liquibase keeps a log and
by oneweekwonder 9y ago
Another options is liquibase[0]. I use the diff[1] tool to create a changeset and then convert it to sql before applying it to my db. liquibase keeps a log and lock table in your db so you can always review the changeset you applied to the db at a later time.
[0] http://www.liquibase.org/ http://www.liquibase.org/
[1] http://www.liquibase.org/documentation/diff.html http://www.liquibase.org/documentation/diff.html
- trampi 9y agoLiquibase is definitifely a good recommendation. We use it to update Oracle, postgreSQL, MariaDB as well as exporting the current schema as a hsqldb-script. Some migrations are only executed for some of our customers.
- robertlagrant 9y agoAlso a big fan of Liquibase here, on SQL Server. I've used Redgate in the past, which is even graphical etc, so simpler to use for slightly less technical DBAs.