XML Schema comparison - difference not spotted!
d.roberts
Posts: 11
We have merged some changes thru several TFS branches such that the TFS database folder has an XML schema Collection in it which is different from the db.
The change has not been picked up by Sql Source Control, and also SQL Compare doesnt spot it.
The change is that a single element has been added:
<xsd:element name="TaxCountry" type="xsd:string" minOccurs="0" />
There doesnt seem to be any options to disable comparison of xml schemas.
We do have several xml schema collections defined - which are in different .SQL files
We think this was probably OK until recently.
we are on SQL Compare v10.3.1.140
SSC version:3.1.4.72
Is this a known issue?
The change has not been picked up by Sql Source Control, and also SQL Compare doesnt spot it.
The change is that a single element has been added:
<xsd:element name="TaxCountry" type="xsd:string" minOccurs="0" />
There doesnt seem to be any options to disable comparison of xml schemas.
We do have several xml schema collections defined - which are in different .SQL files
We think this was probably OK until recently.
we are on SQL Compare v10.3.1.140
SSC version:3.1.4.72
Is this a known issue?
Comments
Sorry, this is not an issue I have seen before. Can can compare XmlSchemaCollection objects successfully out of source control. I'll probably be contacting you by email to ask for some information about how to reproduce this problem.