Defining DBMS preserve options

Chapter 9 Generating Other Models from a PDM

Defining DBMS preserve options

If you generate a PDM into a PDM with a different DBMS, depending on which objects are supported by the old and new target DBMS, you can choose to preserve or lose, the values associated with the following database objects:

Triggers and stored procedures
Physical options for: databases, tables, indexes, primary and alternate keys, default options, tablespaces, and storages
Database objects: databases, storages, tablespaces, abstract data types, sequences
Extended attributes

If a database object is not supported by the old or new target DBMS, the preserve option for that object is grayed and cannot be selected. If the new target DBMS does not support an object, you will lose the values associated with that object when you change target DBMS.

Triggers are rebuilt when a change in DBMS family is made
If you change the target DBMS family, for example from Sybase to Oracle or IBM DB2, triggers are automatically rebuilt