Make SQL Compare easier to use across many database projects by allowing saving project options and filters as template
Each of our production SQL servers has dozens of databases on it. We have a SQL Compare project file for each database to compare it between the production and dev servers.
Sometimes we find out that we've been using different comparison settings (either filters or project settings or both) between databases that results in us not finding differences that we should have, in hindsight, found.
It'd be super if there were a way to define the filters + project settings by at a higher level, and perhaps tied to either the database name, the source server, or the target server.
For example, to be able to say, "Whenever I am comparing between server a and b, and b is the target, then use these settings (from the project options tab) and this filter."
Perhaps this could be implemented by storing the (current) filter and settings outside of the project file in a separate file that would be used by each project file in the same directory.
-
@rich - have you considered using the command line, sqlcompare.exe to achieve this? I'm pretty sure that this can take in a project file as an argument, and you can specify the source and targets as separate switches.