Page 1 of 1
Just updated to the new version and has been disappointed
Posted: Thu 17 Jan 2013 03:20
by dronec
Just updated dbForge Schema Comparison to 3.0.132 and instead of showing what's different between DB objects the app suggests to drop the old SP and create new ones. It just doesn't make sense guys! Please fix or let me know how to rollback to the previous version.
Re: Just updated to the new version and has been disappointed
Posted: Thu 17 Jan 2013 17:53
by sbear
I just had the same experience with dbForge Studio for SQL Server Pro: the update (to 3.0.160) does not make a correct schema comparison. All objects in the source are "Only in the source" and all objects in the target are "Only in the target": everything must be dropped and recreated.
It had worked nicely in the previous version.
Re: Just updated to the new version and has been disappointed
Posted: Fri 18 Jan 2013 07:37
by sbear
This issue seems to be fixed in the just-released 3.0.161!