Synchronized Databases are in read_only after upgrade

[sgtmango333]

We were using Schema Compare version 4.2.35, but needed to upgrade when we installed a SQL Server 2017 instance.

One of the Source servers has read_only databases, but this has never been a problem during synchronization as this property was ignored. After the upgrade the target databases are in read_only. How do I ignore this database property during compare so it is not included in the synchronization script?

[sgtmango333]

Based on the description of the "Compare database properties" Common option, the switch doesn't even matter??

When selected, a database object is included in comparison and synchronization. Note a database object will be synchronized even if the Compare database properties option is turned off, in case the database object is dependent on other objects that are selected for synchronization.

If I'm reading this, the option's setting doesn't really matter; the database properties object WILL be synchronized, period.

Is this correct?

[alexa]

Please try using the 'Compare database properties' option on the 'Options' page of the schema comparison wizard