Just updated to the new version and has been disappointed

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
dronec
Posts: 1
Joined: Thu 17 Jan 2013 03:16

Just updated to the new version and has been disappointed

Post by dronec » Thu 17 Jan 2013 03:20

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.
Top
sbear
Posts: 2
Joined: Thu 17 Jan 2013 17:22

Re: Just updated to the new version and has been disappointed

Post by sbear » Thu 17 Jan 2013 17:53

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.
Top
sbear
Posts: 2
Joined: Thu 17 Jan 2013 17:22

Re: Just updated to the new version and has been disappointed

Post by sbear » Fri 18 Jan 2013 07:37

This issue seems to be fixed in the just-released 3.0.161!
Top
Post Reply

Return to “dbForge for SQL Server”