Migrating records

If you run the Trial utility and create records at the STAGE level, you must promote these records to RUN level to actually compress the database. You can demote records from ARCHIVE to RUN level, which is useful in a recovery situation. You can use the copy function to copy records from test to production or vice versa. You can also use this function for distributed environments.

When you migrate segment registration records created for Custom Huffman compression, the corresponding table records are automatically migrated at the same time. For Shared Tables and Custom Hardware Dictionaries, the table and dictionary records can be shared among many different segment registration records, so a one-to-one relationship does not necessarily exist between the registration and table or dictionary records. You must promote, demote, and copy the Shared Table or Custom Hardware Dictionary independently from the migration of the segment registration records. When you perform the migration process, you must indicate if you want to migrate registration entries, Shared Tables, or Custom Hardware Dictionaries.

When you rebuild a more current copy of a Shared Table or Custom Hardware Dictionary during Trial and then promote the table or dictionary to RUN level, the table ID for the new table or dictionary ID for the new dictionary is different from that of the table or dictionary that was previously being used. The registration records that refer to this Shared Table or Custom Hardware Dictionary do not have to be migrated if they are at RUN level. When the Shared Table or Custom Hardware Dictionary is migrated and if RUN level registration records exist that refer to the table or dictionary, the registration records are updated to reflect the appropriate table ID or dictionary ID. For more information on table and dictionary records, see Defining-table-and-dictionary-records. Figure 1 shows an overview of the record migration panel flow.