[sbuttgereit]

I much prefer the methodology in Sqitch to the migration pattern.

http://sqitch.org/

While I wish the tool had been implemented in something other than perl (with 10 million CPAN dependencies), I like that DDL files are versioned and organized in ways more meaningful to the structure of the database rather than being bound to the timeline of the database.

If I am going to do migrations, a tool like Rambler would have to compare favorably to Flyway (https://flywaydb.org/), which is pretty solid.

[elwinar]

The testing framework of sqitch is pretty cool, I used a something to do database testing a long time ago, but I didn't though of integrating it in the migration tool.

[jdc0589]

i both like and dislike that the registry database is separate. i honestly can't with it how i feel about it.

[sbuttgereit]

The intrusiveness of the registry in terms of database configuration depends on which RDBMS you're using.

I use it with PostgreSQL and I don't use a separate database for the registry. I do have a separate schema for the registry in the same database as the data, but I would want that sort of organization no matter the case. If the database you use doesn't include some sense of "schema" below the database level of separation, I could see how that would be annoying from an administrative/maintenance point of view (or on hosted database solutions).