Redgate Flyway Enterprise

What do you like best about the product?

It’s easy to access the tools needed to generate and migrate scripts. When errors come up, they’re straightforward to navigate, understand, and fix. Performance wise it is top notch and provides seamless integration to vast Databases. The onboarding was helpful to navigate the product.

What do you dislike about the product?

As of now I can't think of any dislikes, the software is friendly and very helpful.

What problems is the product solving and how is that benefiting you?

We used to execute scripts manually and then promote them to subsequent environments. After adopting Redgate Flyway, the process has become faster and easier for promoting DB scripts across multiple environments. It has also helped us establish a consistent base script in all of our developers’ databases. AI support is also great in the application.

What do you like best about the product?

What I like best about Redgate Flyway is its simplicity and flexibility in handling database migrations. It supports

What do you dislike about the product?

If I had to pick something, it might be that Redgate’s tools, while powerful, can sometimes feel a bit premium in pricing, especially for smaller teams. Still, the functionality often justifies the cost.

What problems is the product solving and how is that benefiting you?

It solves the problem of versioning of db scripts and is useful for my project

What do you like best about the product?

Seamless integration with CI/CD for database script deployments

What do you dislike about the product?

Sometimes when there are cert level / infra level issues. Our team will go thru a lot of troubleshooting with our internal global teams and microsoft. Many times Redgate support was not able to provide any resolution.

What problems is the product solving and how is that benefiting you?

Consistency of database schema across DEV/QA/STG/PRD environments. Controlled deployment process and clear drift reports to show what is deployed

What do you like best about the product?

Redgate Flyway is a leading database migration tool that uses a “schema-as-code” approach to help manage database changes efficiently. It integrates smoothly with CI/CD pipelines to automate deployments from development through to production. Flyway also supports over 50 database management systems, helping ensure consistent and reliable database schema evolution across a wide range of environments.

What do you dislike about the product?

What I dislike about Redgate Flyway generally comes down to a few key areas that can slow development workflows and add unnecessary overhead.

First, the learning curve can feel quite steep, especially for teams that are new to migration-based database management. The documentation sometimes seems insufficient, which makes it harder to understand migrations and manage them effectively. As a result, developers can get frustrated and the ramp-up period can take longer than it should.

Another major drawback is the lack of certain features, particularly when important capabilities are limited to paid editions. This “paywall fatigue” comes from seeing functions that feel like they should be standard—such as undo migrations, dry runs, or more advanced reporting—locked behind higher-priced tiers. That can be difficult to justify, especially for smaller teams or projects working with tight budgets.

What problems is the product solving and how is that benefiting you?

In the fast-paced world of software development, managing database changes can often feel like navigating a minefield. Inconsistent environments, manual errors, and the dreaded "it works on my machine" syndrome are common headaches that can derail projects and lead to costly downtime. This is precisely where Redgate Flyway steps in, offering a robust solution to these pervasive problems and bringing significant benefits to our development and operations alike.
One of the primary problems Redgate Flyway tackles is the lack of a standardized, version-controlled approach to database changes. Traditionally, database updates often involved a series of ad-hoc scripts and manual interventions, making it incredibly difficult to track what changes were applied, when, and by whom. Flyway resolves this by treating database migrations as code, allowing us to define, version, and apply these changes systematically across all our environments. This means our database schema is always in sync with our application code, eliminating inconsistencies between development, testing, and production environments. The benefit here is clear: improved quality and reliability, as we can apply the same rigorous standards of version control, testing, and code review that we use for our application code to our database.
Another critical issue Flyway addresses is the potential for manual errors and the resulting unreliability of deployments. When database changes are handled manually, human error is almost inevitable, leading to broken deployments, data corruption, or unexpected behavior. Flyway automates this process, ensuring that changes are applied in the correct order and consistently. This automation not only reduces the risk of errors but also significantly speeds up the deployment process. For us, this translates into greater peace of mind, knowing that what we've tested in a staging environment will reliably be what goes into production. It minimizes the risk and impact of database failures by ensuring our migrations are tested, verified, and even reversible.

What do you like best about the product?

Its versioning system is the best to handle the database issues.

What do you dislike about the product?

One thing I dislike about Redgate Flyway is that the initial setup and migration discipline can feel complex for teams that are transitioning from manual SQL deployments. Teams need to adopt strict versioning practices, and handling scenarios like out-of-order migrations or conflicts between multiple developers requires careful process management.

What problems is the product solving and how is that benefiting you?

Redgate Flyway is helping solve one of the biggest problems we currently face in SCP: managing database changes consistently across multiple environments without relying on manual execution of SQL scripts.

What do you like best about the product?

The UI/UX is well thought out, everything makes sense where it is. It is fast in picking up changes to your database. It can integrate with Microsoft SQL which is a huge plus. The amount of time you save easily justifies the price of the product.

What do you dislike about the product?

Coming from Redgate SQL Source Control isn't an easy migration.

What problems is the product solving and how is that benefiting you?

Source control on my Microsoft SQL databases.

What do you like best about the product?

It brings database changes into the same controlled delivery process as application code. It makes database changes repeatable and auditable for CI/CI.

What do you dislike about the product?

The main drawbacks are the cost, the learning curve, and the complexity of the setup—especially in larger or more heavily customized environments.

What problems is the product solving and how is that benefiting you?

It helps solve the business problem of slow, risky, and inconsistent database delivery. It standardizes database changes across teams and environments, which reduces deployment stress and lowers the risk of out-of-hours releases.

What do you like best about the product?

Flyway was the missing piece for our one click deployment. We had pipelines for the code part of the release, but the database side continued to be our bottleneck as scripts were having to be run manually.

What do you dislike about the product?

There were several database objects that were not supported at the time that required cleanup on our side. Some of these were technical debt in the form of unused and orphaned database objects, but it did take time to track them all down and determine if they could be removed, or needed updating. I believe since then you can set Flyway to ignore certain database objects, so it is likely a non-issue moving forward.

What problems is the product solving and how is that benefiting you?

It is the missing piece for a one click release night. We had the codebase handled with pipelines, but the database side continued to cause issues with the number of changes coming from multiple sources.

What do you like best about the product?

Flyway removes the complexity of generating database migration scripts and has removed 99% of migration script mistakes while also accelerating development time by allowing developers to sync their local DB to the latest structure within minutes.

What do you dislike about the product?

No way for the CLI to be updated automatically on the deployment servers. This means that every upgrade needs to be allied manually to each deployment server.

What problems is the product solving and how is that benefiting you?

Before using Flyway we had manually created change scripts that each developer had to run in order to keep their local development database up to date. These scripts frequently had errors requiring each developer to fix the scripts costing time and money. It also caused problems deploying to test environments with DB updated regularly taking 30+ minutes multiple times per day.

What do you like best about the product?

I like how it’s set up to be fully based on source control, and how easy it is to use.

What do you dislike about the product?

I think the source control policy needs to be top-notch; otherwise, it can fail you horribly during a disaster.

What problems is the product solving and how is that benefiting you?

It helps ship SQL changes across the product in a very organized way for 200+ customers.