Pull filter from source controlled database
When comparing a source controlled database (SSC) to a live database, it would make sense to use the source controlled database's object filter (filter.scpf file) when running the comparison instead of having to manually recreate the filter inside of the SCP project. Also, it would be better if the SCP project stored a link to the filter file used instead of storing the filter string, as it is very inconvenient to have to maintain these separately. If the filter file is changed in SSC, I want SCP to be able to pick up the change automatically.
Mary Hamlin commented
Unfortunately the SCP project stores the content of the SSC filter at the time that you save the project instead of a flag or something to indicate that the comparison should use the SSC filter. The down side of this approach is that if your SSC filter changes, the filter in the project file will still reflect the previous value. As we are using the SCP command line to run our comparisons, so it will make, which will make automation/continuous integration impossible.
The filter should be passed from SQL Source Control to SQL Compare - this was added in SQL Compare v10 and SQL Source Control v2.2.
You should be able to see your SQL Source Control filter in the dropdown list of filters in the top left-hand corner of the Comparison Results screen in SQL Compare.
Please let us know if this doesn't do what you'd expect or if you need any more help with filters.