Release create-tables script

Only changed tables

The resulting script refers only to tables that have changed compared to a previous situation. In a Delivery Manager context, that previous situation is the previous release. If there is no previous release (ie., if the current release is initial), then all tables are considered "changed".

Only local or consumed tables

•If "Application" is registered as the Top-level application in Delivery Manager, then tables defined in the application itself are included in the script, and tables defined in consumed module applications are also included in the script.

•If "Application" is registered as a Module application in Delivery Manager, then only tables defined within the module application are included in the script.

Only tables registered as Application Table in Delivery Manager

The resulting script refers only to tables registered as Application Table in Delivery Manager. You can bring the list(s) of Application Tables up-to-date by running the " Populate tables list " action for each application.

The list of tables for the top-level application includes consumed interface tables, but not tables defined in modules that have Interface = No.

Only tables that are not skipped

The resulting script refers only to tables registered as Application Table with the Skipped = No setting (the default).

In the case of consumed interface tables, the table will be listed both for the top-level application and also for the module. If you call the "Release create-tables script" action for the top-level application, then the value of Skipped in the list of tables for the top-level application determines whether the table is skipped or not.

For each table in scope, and depending on the exact syntax required by the RDBMS, Delivery Manager automatically generates all DDL statements (CREATE TABLE, ALTER TABLE...) and DML statements (INSERT, UPDATE) required to bring the database state from the previous release to the current release. Indexes are dropped and re-created.

Outside Delivery Manager, depending on context, USoft tools automatically generate either CREATE TABLE or ALTER TABLE statements. In Delivery Manager, you can use upgrade hints to choose, on a per‑table basis, whether you want to generate a CREATE TABLE or an ALTER TABLE statement.

"Release is non-initial but XML repository file for previous version is not found at folder."

Explanation: It is not possible to determine what are the database changes in this release because information on the database state in the previous release is not, or no longer, available.

How to fix: If you have a backup of the application state at the time of the previous release, perhaps on a target machine that you have copied the deliverables of the previous release to, then copy that backup file to the \metadata directory of the previous release folder, making sure you use "application.USD.xml" as the filename. To set the previous state to the current state, run the "Export metadata" action for the application, making sure you export to the \metadata folder of the previous release.

"XML repository file for module not found at: folder."

Explanation: You are attempting to release a create-tables script for the application registered in Delivery Manager as the top-level application, and module is an application registered in Delivery Manager as a module consumed by this top-level application. In order to generate a full list of database tables to be created, an XML repository file of each module is required in the \metadata folder because this describes any database tables defined in the module but not known to the top-level application (because not an interface table).

How to fix: Run the "Release metadata" action for the module.

You can customise the create-tables script that Delivery Manager releases. This is possible because Delivery Manager writes to the release folder all the XML input files used for the script generation, as well as the XSLT transformation used to generate the SQL script.

To customise, you need to understand the different steps that Delivery Manager takes to generate a create-tables script.

Calling "Release create-tables script" is different from calling USoft's standard "Create Physical Tables" option, as executed by the "Generate create-tables script" routine, because :

•"Release create-tables script" is based on a comparison with metadata as defined for the PREVIOUS release and registered in Delivery Manager's previous release folder, whereas

•USoft's standard "Create Physical Tables" option is based on whatever database state is found on the local machine where the option is run. To execute this standard option from Delivery Manager, if you want changes to apply immediately to the repository, call " Create tables from repository ". If you want to write the changes to a script file, call " Generate create-tables script ".

Instead of calling "Release create-tables script", you can alternatively call "Release scripts" with "Include physical tables upgrade script" = Yes. The result is identical.

The only difference between "Release create-tables script" and "Release scripts" is that "Release scripts" also releases other upgrade scripts (if any exist for the current version of "Application").