dbForge Schema Compare for Redshift/PostgreSQL Reviews

DBForge has the option to compare the data in both Postgres and Redshift. We are performing the data migration and upgradation. We will be using this comparer tool to compare the data.

Other than the data Comparison, if it also has the other objects comparison, it will be good. Stored Procedures also needs this type of comparison using this tool

Time-Saving tool to compare the data between two homogenous databases. It is especially getting used in migration and upgradation activities. This will benefit the Business to deliver the projects within the deadlines.

.It's very easy to use and is priced right!

From what I know about the tool, there is not much to dislike

The problems schema compare resolved was to identify the differences between our development, test and production environments

I use this tool to compare the production and non-production instances of our enterprise data warehouse on AWS Redshift which has 30+ TBs of data spread throughout 1000+ tables. dbForge can seamlessly connect to both of our Redshift instances and maintain that connection continuously. The way it filters out identical and different tables/views is very helpful and easy to identify. Side by side view of both DDLs is great to capture the differences fast. SQL query editor is awesome that it can give suggestions better than most of the well-known DB Clients out there (It creates the catalog out of 1000+ tables/views in many different schemas pretty fast and intelligent enough to give suggestions across aliases as well). UI is also fairly intuitive and user-friendly. Dark skin is also really good and naming the skins is clever in relation to the mostly used MS Office and Visual Studio (Office Black, Visual Studio Dark, etc) so that the user can expect the same color theme as his/hers mostly used software (This is the first time I'm seeing a naming like this !).

dbForge tool is really good, so I'd probably be nitpicking here. The first time I tried to create a new DB connection, I thought it should be there under "File" -> "New", but it was not since they have a separate menu as "Database". So I still think "New Connection" should go under "File" -> "New" for it to be more intuitive to a first-time user. I use the "Object Filter" side pane menu all the time to filter what I want to see from tables, views, schemas, etc, but it is not resizable so it has a lot of space unused because it only takes a little to show the names "Functions", "Tables", "Views", "Schemas" etc. When viewing the data results of a table with many columns, it's hard to find one column so it will be easier if the tool has a column search.

We have not yet set up a CI/CD mechanism to migrate the tables and views from our non-production database to the production Redshift database. So it's essential for us to see the differences between the DDLs in non-prod and prod to do a proper production deployment. Checking the differences is also useful to identify the new modifications to be done in the non-production environment related to the new features/data additions to the warehouse.