Load Legacy Data Into Staging Tables
This section provides some high level discussion about mapping and loading legacy data to the system's staging tables.
Mass Load Utility
Unless in a Cloud installation, you can use any method you prefer to load data from your legacy application. However, we recommend that you investigate your database's mass load utility (as opposed to using insert statements) as the mechanism to load the staging tables. In addition, we strongly recommend that you disable the indexes on these tables before populating these tables and then enable the indexes after populating these tables.
Populating Keys
Some tables in the staging database have keys that are system-assigned random numbers. Special consideration should be given when populating these keys. Refer to A Note About Keys for more information on how to properly populate these tables. Those tables that don't have system-assigned random numbers have keys that are a concatenation of the parent's prime-key plus one or more additional fields.
Populating Characteristic Tables
- Predefined. Populate search characteristic value with the contents of the characteristic value column converted to upper case.
- Ad hoc. Populate search characteristic value with the first 50 bytes of the ad hoc characteristic value column converted to upper case.
- Foreign key. Populate search characteristic value by concatenating the values of each foreign key characteristic value column to a maximum of 50 bytes.