Atlas Cloud by Ariga vs. Redgate Flyway

If your application is running on many environments then some kind of automation for database migrations should be implemented. This will save time and trouble for employees and helps to manage migrations. However it must be understood that it is not a magical tool & should be studied properly so that it's limitations are understood & it will be used properly. Otherwise it might cause problems to the application.

Incentivized

• Keeps track of migrations
• Makes it really easy to version and review queries
• Helps you understand what you have deployed, where super easily

Incentivized

• For the script, especially for inserting a new row of data, I'd like to see to use if not exists, then insert, else just update.
• When we run the script, it will error out if we use not exists for inserting new table rows.

It's very easy to install and use. Even someone very new to the software will have no trouble, plus the team reach out to help you and continue to offer you support throughout. Really simple interface, clean design, all you could really ask for in a tool that needs to do a job dependably

Incentivized

The problem with a cloud-based tool for migration services is the cloud dependency. You are restricted to use the tool along the Cloud provider. Flyway gives you the freedom to use it in any scenario as long as you are working with a compatible database engine. Even if you are working on-premise and you don't have plans to move to a cloud architecture. Or even for sandbox development scenarios where you are a developer playing around with some project ideas. And you don't have to pay anything as long as you need advanced features, and not less importantly, you are using an open-source tool.

Incentivized

• DB migration is fully automated
• DB migration is committed to source code, repeatable on all environments
• DB migration is fully integrated into development cycle

Incentivized