This appendix includes the following sections:
RegisterSchema can be handled by registering the schema definition on both source and target databases before any table is created that references the XML schema.
DeleteSchema on the source database first. Once Replicat is caught up with the changes made to the source database, issue the
DeleteSchema call on the target database.
The CopyEvolve procedure evolves, or changes, a schema and can modify tables by adding or removing columns. It can also be used to change whether or not XML documents are valid. Handling
CopyEvolve requires more coordination. Use the following procedure if you are issuing
CopyEvolve on the source database.
Quiesce changes to dependent tables on the source database.
CopyEvolve on the primary or source database.
Wait for Replicat to finish applying all of the data from those tables to the target database.
CopyEvolve on the target database.