G2

Robby Gunawan S.

Founder

Computer Software

Small-Business (50 or fewer emp.)

9/17/2019

"Great tools for comparing schema and data in a short time"

5/5

What do you like best about dbForge Compare Bundle for SQL Server?

This tool is simple, straightforward, and easy to use. You can compare schemas or data using the default settings in three steps, or, if you want more detail, you can adjust the advanced settings. The comparison process is fast—within seconds you get results showing which data or schema is different.

You can also save your own comparison settings instead of using the default settings from Devart; just load your saved settings and click Finish to run the comparison. After the comparison is complete, it shows the different table schemas or the number of data differences from the source server to the target server, and you can choose which tables or data you want to change.

Once the process is finished, you get a result summary that includes which steps failed or succeeded. I hope the next version of the compare bundle adds rollback and commit functions, so when we update a production server and something goes wrong, we can roll back the changes. Review collected by and hosted on G2.com.

What do you dislike about dbForge Compare Bundle for SQL Server?

Some case, when the different data is huge (more than 10k different data), process sometimes stop, not responding, but process still run until finish Review collected by and hosted on G2.com.

Recommendations to others considering dbForge Compare Bundle for SQL Server:

Pricing is little high but it's worth to buy, compare with how long you checking manually one by one field every single table in your database or implement new version apps with database changes.

this tool must have by programmer or database administrator in software house Review collected by and hosted on G2.com.

What problems is dbForge Compare Bundle for SQL Server solving and how is that benefiting you?

Every programmer faces this problem when moving from a development server to a production server: sometimes we forget certain changes, or a bug slips into the program. In those cases, we need to copy data or compare data between the development and production servers. Before I used this program, I would spend half a day synchronizing table schemas or data from development to production, especially when I was adding a new feature, such as creating a new table or changing an existing table schema. Review collected by and hosted on G2.com.