Primary Key Sequencing in the Destination Database

The application uses a database sequence object to generate unique values for primary keys (PK). During the migration process, after data is migrated from the source database to the destination database, the destination database sequence number is updated based on the next available value in the PK column.

If the table attribute staticIDs=“true”, then the data columns in the destination database will retain the same PK values (i.e., sequence numbers) as the source database. However, if the table attribute staticIDs = “false”, then the destination columns will be updated with the next available sequence number.

For example, if the TIME_CODE PK value was 10001 in the source database, and if <table name="TIME_CODE" staticIDs=”true”>, then upon migration, the TIME_CODE PK value for the same record in the destination database would also be 10001. However, if <table name="TIME_CODE" staticIDs=”false”>, then the system would pick up the next available sequence number and assign it to the record.

The staticIDs attribute is stored in the core schema (schema.xml) and custom schema files. Here is an example, in schemal.xml, where table WB_LOCALZD_TBL is set to attribute “staticIDs=”true”:

<table name="WB_LOCALZD_TBL" staticIDs="true">
	<uk>
		 <field column="WBLT_TB_NAME" /> 
	</uk>
</table>