Copying UET table schema changes

If one site contains UET modifications to a table, but the same table in another site does not contain those modifications, errors probably will be generated during replication of that table’s data from one site to the other.

For that reason, before you replicate data between sites, you should copy any UET schema changes to all sites involved in the replication. A stored procedure, ExportUETClassSp, assists in handling this process. When you run ExportUETClassSp on one site, you create a SQL script file that you can apply to other sites, so that the table schemas on both sites are identical.

  1. Disable replication at all sites.
  2. At the site with UETs, run the ExportUETClassSp stored procedure.
    This stored procedure creates several scripts.
  3. At each of the other (target) sites that need to replicate data to/from the site with UETs, apply the scripts generated in the previous step.
  4. At each target site, run the Factory Track UET Impact Schema form/utility.
  5. Enable replication at all sites.
  6. Regenerate replication triggers at all sites.