Liquibase VS DBConvert Studio

Liquibase Reviews

DBConvert Studio Reviews

1. markus-patt    

   over 3 years ago

   Good alternative to other migration tools, has many features and settings,i am migrating my databases fastly to my web server on regular basis.

   🏁 Competitors: Full Convert

   👍 Pros:    Fast conversion speed|Good responsive interface|Low price
2. Tim    

   IT Manager at Kalahari Research Trust | over 3 years ago
   Great tool with super customer support and tailored advice

   Great tool! Our research trust has been using this tool for the last 5 years. We have received a lot of support which was very personal and due to the complexity of our MS access database even a customisation was made to the program to be able to import all our records without any problems. I highly recommend this tool for migration, but also in our case for daily synchronisation of an active MS Access database to MySQL.

   👍 Pros:    Efficient|Lightweight|Great customer support|Highly customizable
3. Samuel    

   db assistant | almost 4 years ago
   good migration program

   I'm using DBConvert Studio for replicating many MySQL databases to Postgres and it is very handy so it's quite powerful tool for doing such jobs.

Liquibase mentions (5)

• How do you guys go about the persistence layer?

  As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago

• How do you guys go about the persistence layer? (x-post)

  I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

• Where questioning the scale of a company and its clients its seen bad

  Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago

• State based change management tool for Snowflake

  I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago

• Learning SQL and using dll (CREATE,DROP,ALTER)

  Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago

DBConvert Studio mentions (0)