Database Constraint Handling
- Invalid data that should not be migrated. The most common invalid data of this type is residual data left over from an incomplete delete operation. The migration wizard will not migrate data of this type to the new database. The migration log file will contain a note if any such items are encountered during the migration. See the Migration Log Only Constraints section.
- Invalid data that is easily salvageable. The migration wizard will recover any such data and migrate the recovered data into the destination database.
- Invalid data that may be salvageable, but may be handed by more than one method. The migration wizard contains an option to perform a pre-migration data integrity check, which checks for this type of constraint violations. The results of the check will list any violations it encounters, how the migration wizard will handle the situation if no preemptive action is taken, and what the user may try to do to salvage the data before migrating the database. See the Pre-migration Data Integrity Constraints section.
For more information on a specific upgrade or migration topic, return to the upgrade and migration home page.