I noticed in sql compare 8 RC all objects are now selected by default again. Can we just make this an application option for whether the different objects are selected by default or not?
jamal
0

Comments

4 comments

  • PDinCA
    I'd like to second this suggestion.

    Pre-selecting is frequently inconvenient and can lead to inadvertantly migrating changes - mistakes happen! "First do no harm" is best implemented by having nothing preselected... Please, however, keep the useful feature that retains checked objects when a refresh is performed and the objects are still different - that's immensely helpful...

    In the case where the source DB is SQL Server 2000 and the target is 2008, MANY differences are detected that really are simple version-differences, e.g., STATISTICS add the PK and SQL Compare says "that's a difference". To have these auto-selected is unnecessary.

    Thanks.
    PDinCA
    0
  • David Atkinson
    Does this happen for new projects or only existing ones? I think we chose to preserve the state of the existing ones, but you can change this using the checkboxes above the synch column.

    David Atkinson
    Red Gate Software
    David Atkinson
    0
  • brian.merz
    With the way I use SQL Compare, pre selecting everything is a great aid. I have multiple development servers to keep in line for nightly builds with the team.

    Since there is strong demand for both default select all and select nothing I can get behind the idea of adding this to the application options. I won't object too much if the default is select nothing and I have to go into options once and check the select all checkbox. So long as there remains a way to default select everything I'm happy. :)
    brian.merz
    0
  • David Atkinson
    Once you've clicked on the 'select all' checkbox, this will be remembered with the project (as well as checkbox selections for each grouping). Only 'new' projects will revert to everything deselected and I guess we're asking our users who want all objects selected to click once when they set up a new project. We could have an option, but this is potentially dangerous for users who maybe use SQL Compare on a colleague's machine and might assume that deselection is the default behaviour. Of course if we believe that it's too much of an annoyance for a significant proportion of our existing users we could consider adding an application option.

    David
    David Atkinson
    0

Add comment

Please sign in to leave a comment.