D Supporting Changes to XML Schemas
Topics:
- Supporting RegisterSchema
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. - Supporting DeleteSchema
IssueDeleteSchema
on the source database first. - Supporting CopyEvolve
The CopyEvolve procedure evolves, or changes, a schema and can modify tables by adding or removing columns.
Supporting RegisterSchema
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.
Parent topic: Supporting Changes to XML Schemas
Supporting DeleteSchema
Issue 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.
Parent topic: Supporting Changes to XML Schemas
Supporting CopyEvolve
The CopyEvolve procedure evolves, or changes, a schema and can modify tables by adding or removing columns.
The CopyEvolve procedure 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.
- Execute the
CopyEvolve
on the primary or source database. - Wait for Replicat to finish applying all of the data from those tables to the target database.
- Stop Replicat.
- Apply the
CopyEvolve
on the target database. - Restart Replicat.
Parent topic: Supporting Changes to XML Schemas