Troubleshooting: Avoid copying full table copy when Unique/Primary key is updated

Symptoms

If there are lots of records (for example, more than 50000) in the database dictionary whose Unique/Primary key is updated by Upgrade Utility, the system may copy the full table and take much time to update these records.

Resolution

Follow these steps:

1. Before upgrade, run the SQL Compare utility and check the except.log file. You may find some information similar to the following example:

   dbdict:cirelationship, Unique Key is {"relationship.name", "logical.name"} -- the Unique key is removed or updated and may cause full table copy.

   This information indicates that the Unique key will be removed or updated during the upgrade process and may cause full table copy.

2. After loading the tranfer.bin file in the upgrade wizard, open upgradeKeyChanges in the ScriptLibrary, and then search for the following codes:

   var DBDICT_IGNORE_UNIQUE_KEY = [];

   Update it to:

   var DBDICT_IGNORE_UNIQUE_KEY = ["cirelationship"];

3. Save the ScriptLibrary and then continue upgrading. The Unique/Primary key of the record will not be updated.
4. After upgrade, you need to update the Unique/Primary key manually.