different but not selected for sync

NTownsley

when comparing two databases, items are determined to be different but not automatically selected for synchronization, but others are. We end up reviewing 20 objects to simply determine that yes the stored proc should be synchronized. The odd thing is it seems to be a very clear difference in every case.

I'm sure this has been covered before, but i have searched and cannot determine the answer...

Michelle T

By default, new objects are not selected for synchronization, to help avoid accidental synchronizations. So any object which your project hasn't seen before will show up with an empty check box.

If you customarily synchronize everything it should be fine to just check everything - you can use the check boxes in the grouping bars to check/uncheck everything in the group, or the one in the column headings row to check/uncheck everything in the comparison.

This was changed from previous versions which would select everything by default due to requests from some people who found the 'always select new objects' behaviour dangerous.

Does that answer your question?

NTownsley

does it also hold true that synchronization that could cause a drop of a trigger for instance on the destination database would also not be automatically selected? basically anything deemed "destructive" would require review?

Chris Auckland

It should do. By default, all objects will be unchecked for synchronization.