Keys and Relationships

Archiving configuration data that is based on user-defined keys can be problematic. Since configuration tables' keys are user-defined (not system-generated), they do not have associated key tables. This means that if you archive configuration data, the system does not validate that the key has been used once it has been moved to an archive environment's database.

Remember that one of the features of an archive environment is that it provides you the ability to use the application to view both production and archived data at the same time. By logging into an archive environment whose application server points to the CISREAD schema, the data is presented from super views of both production and archive. If data related to a user-defined key were re-used in production, the super view in archive would contain two records with the same key value, and the effect on the archive environment would be unpredictable. You should consider carefully whether you want to archive data based on user-defined keys.

Fastpath: For more information on how data based on system-generated keys vs. data based on user-defined keys is handled during an archive, refer to Step 4: Move or Delete Production Data.

CAUTION:

It is possible to contort the archive and purge processes to introduce problems for the super views in an archive environment. If, for example, you archived bills with bill calculation headers that referenced a rate version, then purged that rate version from production, the archive environment would not have access to the rate version needed to view those archived bills.