Building and Running Application Schema Metadata Scripts

You can dump the metadata into SQL scripts which can then be loaded into other application databases, for example at other sites where the same table/column changes are being made.

The document Insert and Update Trigger Generation explains in much greater detail the specifics of this metadata and its use in the system.

Follow these steps:

In one site, define the metadata as described above.
Use the Generate Application Schema Metadata Scripts form to create these scripts, as needed:
- Module metadata, which was defined in the Application Schema Modules Metadata form
- Tables metadata, which was defined in the Application Schem Tables Metadata form
- Column (Next Keys) metadata, which was defined in the Application Schema Columns Metadata form.
If you use this application with APS, use the Generate Application Schema Metadata Extensions Script form to create a SQL script with table-based attribute extensions metadata.
Load the SQL script(s) into other sites (application databases), which must also contain any applicable new or modified schema elements.
At these other sites, use the Trigger Management form to generate triggers for specified tables.