Redgate Flyway Enterprise
RedgateExternal reviews
83 reviews
from
External reviews are not included in the AWS star rating for the product.
Version-Controlled Database Migrations with Seamless GitHub/GitLab CI/CD Integration
What do you like best about the product?
Redgate Flyway helps you version-control database schema changes in the same way you version application code, and I find that extremely helpful. It also integrates with GitHub and GitLab for CI/CD, and those integrations are the features I appreciate most about Flyway.
What do you dislike about the product?
Handling rollbacks feels a bit more complicated than it should be, and I’m left thinking there might be a clearer, more straightforward way to do it.
What problems is the product solving and how is that benefiting you?
Usually, database changes aren’t kept under version control, and Flyway helps solve that by bringing version control to database-related queries and migrations. It makes it easier to track what changed, when it changed, and keep those updates consistent across environments.
Excellent for CI/CD Use Cases and Schema Evolution in Data Pipelines
What do you like best about the product?
CI/CD use cases and schema evolution in data pipelines
What do you dislike about the product?
: In the Community (free) edition, there is no built-in undo command. If a migration fails or you need to roll back, you have to manually script the reversal or "migrate forward" with a fix.
What problems is the product solving and how is that benefiting you?
Redgate Flyway acts as a bridge between the fast-moving world of application code (Git, CI/CD) and the traditionally slow, manual world of database management.
By solving the "database bottleneck," it benefits teams by ensuring that a database is never out of sync with the application it supports. Here is a breakdown of the core problems it solves and the tangible benefits of using it
By solving the "database bottleneck," it benefits teams by ensuring that a database is never out of sync with the application it supports. Here is a breakdown of the core problems it solves and the tangible benefits of using it
Integrates Smoothly with SQL Management Studio
What do you like best about the product?
It integrates well with SQL Management Studio
What do you dislike about the product?
I did not get integrated with the latest version
What problems is the product solving and how is that benefiting you?
that can standardize and automatically indent my code
Structured DB Releases with Reliable Shadow DB Migration Checks
What do you like best about the product?
it helps to organize db release in a more structured way and it is quite helpful to always check the migrations on a shadow db
What do you dislike about the product?
Still not sure how exactly the sampling of the data works, and sometimes managing the migration out of sync is bit difficult
What problems is the product solving and how is that benefiting you?
like I mentioned previously organizing the release in a more structured way is quite helpful
we no go through the same pr process to manage it
we no go through the same pr process to manage it
Easy-to-Use, Simple UI with Straightforward Integration
What do you like best about the product?
It’s easy to use, with a simple, non-complex UI. Integration is also easy and straightforward.
What do you dislike about the product?
linear versioning can cause major headaches during parallel team development, leading to frequent naming conflicts and merge issues
What problems is the product solving and how is that benefiting you?
solves the chaos of manual schema updates and environment drift by treating database changes as version-controlled code
Predictable, Automated Database Migrations with Version-Controlled SQL
What do you like best about the product?
Redgate Flyway excels by treating database migrations as version-controlled SQL, ensuring deployments are predictable, automated, and consistent across all environments.
What do you dislike about the product?
Flyway is great for simple, linear schema changes, but it becomes restrictive when migrations require complex conditional logic or environment-specific behavior.
What problems is the product solving and how is that benefiting you?
Redgate Flyway solves the problem of version-controlled, repeatable database migrations by applying schema changes in a consistent, ordered way across environments. This ensures that all teams and environments stay in sync, reduces deployment errors, and makes rollouts more predictable.
For me, this benefits development and deployment by providing traceable change history, automation-friendly migrations, and a standardized process that aligns with CI/CD pipelines, reducing manual intervention and drift between environments.
For me, this benefits development and deployment by providing traceable change history, automation-friendly migrations, and a standardized process that aligns with CI/CD pipelines, reducing manual intervention and drift between environments.
Overall Redgate is good, and easy and help to make things automated.
What do you like best about the product?
Redgate integrates easily with a version control system, and it also connects smoothly with CI/CD. This makes it much easier to manage the CI/CD pipeline without having to worry about other things.
What do you dislike about the product?
The documentation really needs improvement, and adding screenshots would make the setup much easier to follow. As it stands, it isn’t very helpful, and the setup process ends up feeling unnecessarily complicated.
What problems is the product solving and how is that benefiting you?
I was facing a CI/CD-related problem that made handling SQL queries far too complex. After using Redgate, it became much easier to manage and handle those queries.
Simple, Version-Controlled Migrations That Fit Naturally into CI/CD
What do you like best about the product?
I like how Redgate Flyway gives you simple, version-controlled database migrations that fit naturally into CI/CD pipelines.
It keeps schema changes transparent, repeatable, and easy to roll forward with confidence.
It keeps schema changes transparent, repeatable, and easy to roll forward with confidence.
What do you dislike about the product?
I dislike that complex rollback scenarios can be tricky and often require manual scripting.
Also, advanced features are locked behind paid editions, which can be limiting for smaller teams.
Also, advanced features are locked behind paid editions, which can be limiting for smaller teams.
What problems is the product solving and how is that benefiting you?
Redgate Flyway solves the problem of uncontrolled, manual database changes by enforcing versioned, repeatable migrations.
That benefits me by making deployments safer, auditable, and consistent across all environments.
That benefits me by making deployments safer, auditable, and consistent across all environments.
Simple, Transparent SQL-Based Migrations with Easy Version Tracking
What do you like best about the product?
The absolute best part is the simplicity of the plain SQL-based migrations. I don’t have to learn a proprietary XML or YAML DSL to manage my schema changes. It treats my SQL as a first-class citizen, and the linear, version-based execution makes it incredibly easy to reason about the state of our database across different environments. It’s transparent, and there’s no 'magic' happening behind the scenes that I can't debug.
What do you dislike about the product?
The gap between the Community and Teams/Enterprise editions can be frustrating. Basic necessities for a production environment like Undo migrations or Dry Runs are locked behind a pretty steep paywall. It’s tough to sell the 'fail-safe' aspect of the tool to management when the safety net (Undo) isn't in the free version we used for the POC.
What problems is the product solving and how is that benefiting you?
It basically stops the 'it worked on my machine' syndrome for databases. By automating our migrations, we’ve moved away from the nightmare of tracking which SQL scripts have run where.
It benefits me by saving a ton of time, I'm not babysitting deployments or manually diffing tables anymore. I can just write my SQL, check it into Git, and let the automation handle the heavy lifting. It’s made our release cycle way less stressful.
It benefits me by saving a ton of time, I'm not babysitting deployments or manually diffing tables anymore. I can just write my SQL, check it into Git, and let the automation handle the heavy lifting. It’s made our release cycle way less stressful.
Flyway Makes Database Migrations Simple, Structured, and Reliable
What do you like best about the product?
What I like most about Flyway is how simple it is and how it encourages a structured workflow. Compared with similar tools, it feels easier to use, and with just a few commands I can take care of everything I need. At the same time, it pushes me to follow proper migration practices that I might otherwise overlook, which makes the overall process more reliable and consistent.
What do you dislike about the product?
I dislike that it’s hard to find a proper way to use it with a database that’s already in production and wasn’t using Flyway from the start.
What problems is the product solving and how is that benefiting you?
It solves the problem of keeping database scripts in sync across multiple environments by integrating seamlessly with Git. I don’t have to waste time manually coordinating changes, and I don’t worry about forgetting to apply a script somewhere.
showing 21 - 30