I store the last time a database was synchronized in a separate table, both on my internal systems ans well as external systems. This has proven to be quite handy in the past. Unfortunately it also requires that I open each script in Management Studio and add my update the last sync date code by hand.
In my setup, I have multiple databases to keep in sync across multiple servers. As such I run the same file against each database and physical server. Typically this file gets moved to each physical server and then run against the databases in question. To avoid accidental execution of a new sync script (breaking the F5 habit is hard), is it possible to add an option to NOT connect to the target server when loading Management Studio from SQL Compare? This would be especially handy if it could be selected on a per project level as opposed to the application level.
Thanks!
To work around this for the time being, you could select 'Custom Program' in Application Options and point that at Management Studio, passing it only the script file name. This is a little fiddly and is application-wide rather than project-based, but might help for the moment
.
In my setup, I have multiple databases to keep in sync across multiple servers. As such I run the same file against each database and physical server. Typically this file gets moved to each physical server and then run against the databases in question. To avoid accidental execution of a new sync script (breaking the F5 habit is hard), is it possible to add an option to NOT connect to the target server when loading Management Studio from SQL Compare? This would be especially handy if it could be selected on a per project level as opposed to the application level.
Thanks!