Firstly, congratulations on a huge move forward since the alpha 8)
Two things that strike me straight away are (for SQL Compare)
- The inability to not save changes to a project, and
- The necessity to re-register databases when altering comparison options
A typical example of wanting to not save a project is where I compare a given project, spot one or two objects that I don't want to deploy (yet), so de-select them, then run the synchronise wizard. If I don't remember to re-select the objects I excluded, they'll be excluded next time.
Note that I'm not suggesting that SQL Compare shouldn't remember my exclusions - it should - but only if I save the project. I should have an option to close without save to revert back to the last saved version.
The re-registration relates to the scenario where I have registered both databases, but realise (based on the number of different objects) that I have a badly set option (for example not ignoring constraint names). I change the option to ignore constraint names, and while I do want to re-compare, I would prefer to avoid the delay involved in re-registering both databases.
I'm sure I'll have plenty more comments to follow up with (two I know of right now, but I have to go back and check to see if you've slipped these features in since the alpha, but I can't find them :oops:), but so far a good start to the beta.
Two things that strike me straight away are (for SQL Compare)
- The inability to not save changes to a project, and
- The necessity to re-register databases when altering comparison options
A typical example of wanting to not save a project is where I compare a given project, spot one or two objects that I don't want to deploy (yet), so de-select them, then run the synchronise wizard. If I don't remember to re-select the objects I excluded, they'll be excluded next time.Note that I'm not suggesting that SQL Compare shouldn't remember my exclusions - it should - but only if I save the project. I should have an option to close without save to revert back to the last saved version.
The re-registration relates to the scenario where I have registered both databases, but realise (based on the number of different objects) that I have a badly set option (for example not ignoring constraint names). I change the option to ignore constraint names, and while I do want to re-compare, I would prefer to avoid the delay involved in re-registering both databases.
I'm sure I'll have plenty more comments to follow up with (two I know of right now, but I have to go back and check to see if you've slipped these features in since the alpha, but I can't find them :oops:), but so far a good start to the beta.