Below are the some of the migrateSystem properties which controls the tasks performed by the migrate script:
pega.clone.generate.xml - During this step, the script reads the provided source schema (pega.source.rules.schema) using metadata queries, capturing the DDL in an xml format. This step can be run atomically in the case that the two database systems (production and upgrade) are separated by a firewall. No changes are made to the database during this step.
pega.clone.create.ddl - This step uses the captured xml from pega.clone.generate.xml and generates the DDL for the target schema (pega.target.rules.schema). This step can also be run atomically, but requires that the pega.clone.generate.xml has been run. Running this step atomically also allows the user to review the generated ddl before applying it to the new schema. No changes are made to the database during this step.
pega.clone.apply.ddl - This step applies the DDL generated by pega.clone.create.ddl to the specified target schema (pega.target.rules.schema). This step can also be run atomically, but requires that the pega.clone.create.ddl step has been run. This step creates new tables, views, stored procedures, and functions in the specified target schema.