XML SCHEMA dependents prevent drop

cleek

I have a stored procedure that has a parameter that is bound to an xml schema collection. The xml schema collection has changed. Because the xml schema collection is different between the source and target databases, the SDK tries to drop the xml schema collection and recreate it. However, the xml schema collection cannot be dropped, because it is still bound to a stored procedure parameter. Is this expected behavior? What is the recommended algorithm for synchronizing an xml schema collection that has changed and has dependent objects? Is there a way to update the xml schema collection without manually dropping the XmlSchemaCollection's dependent objects and then rerunning the comparison and update?

xsinc.msanders

8 years later. I must also know this.

xsinc.msanders

It seems the workaround is to deploy the dependencies..