Comments
Sort by recent activity
Where do we vote? [image]
The ability to retain the results of the previous comparison and the tables/rows selected for synchronization would be a huge benefit to me. Of course, it may be necessary to add a prompt when opening a project with saved synchronization info to the effect of, "The underlying data in the tables you are comparing may have changed. Do you want to refresh the comparison?" or something like that.
Even if the underlying data has changed, if the rows selected for synchronization are identified by primary key, it should be possible to retain the selections even after comparison is refreshed.
Also, since saving the comparison results, along with selected rows, could create extremely large files (I have a separate volume just for Red Gate temp files; since I use Data Compare on tables with hundreds of thousands of rows the temp files can take up a couple GB at times), the feature to save comparison results and selections should be a project option, not set by default. / comments
Where do we vote?
The ability to retain the results of the previous comparison and the tables/rows selected for synchronization would be a huge benefit to me. Of course, it may be necessary to ...
Add my strong vote to this one.
Is there a central "feature request" list somewhere that we can vote on or reply to feature/fix requests? It seems like there must be, but I feel dumb for not being able to find it... / comments
Add my strong vote to this one.
Is there a central "feature request" list somewhere that we can vote on or reply to feature/fix requests? It seems like there must be, but I feel dumb for not being...
I vote for triggers to be compared as separate objects. After all (and I know I'm just instructing people who already know this), Triggers are just stored procedures tied to a specific table's events. I don't think they should be treated as "extended properties" of the table. / comments
I vote for triggers to be compared as separate objects. After all (and I know I'm just instructing people who already know this), Triggers are just stored procedures tied to a specific table's eve...
Removing this feature was a TERRIBLE idea, and it should be brought back in SQL Compare 6. I have to compare ERP databases between our Development and Test environments (we're a manufacturing company), and the "Registering Databases" step alone takes 35 minutes. Many times all I need to do is compare changes to tables, or stored procedures, or triggers, and NOT the entire database. / comments
Removing this feature was a TERRIBLE idea, and it should be brought back in SQL Compare 6. I have to compare ERP databases between our Development and Test environments (we're a manufacturing comp...