Administer > Database administration > Case-sensitivity > Load/unload implications of case-insensitivity

Load/unload implications of case-sensitivity

When you load/unload data from a Service Manager system that connects to a case-sensitive database and load it into one that connects to a case-insensitive database, you can choose whether you want to Add and Update records or to Only add new records.

  • If you select Record Load Options - Add/update records, the new records will be inserted into the table and the existing records will be updated.
    • Example 1: Suppose that you use a case-sensitive database to create an unload file that has two operator records - "operator01" and "operator02". You then load this unload file into a case-insensitive database which already has an operator record "OPERATOR01". In this case, "OPERATOR01" will be updated by "operator01" and "operator02" will be added.

      Note: If you try to load records with unique IDs that differ only in case from records that already exist in the case-insensitive database, the data in the unload will update the data in the current system.

    • Example 2: Suppose that you use a case-sensitive database to create an unload file that has two operator records - "operator01" and "OPERATOR01". You then load this unload file into a case-insensitive database which already has an operator record "OPERATOR01". In this case, "OPERATOR01" will be updated by "operator01" and subsequently by "OPERATOR01", or visa-versa depending on the order of those records in the unload file.

      Note: If you try to add/update two records with unique IDs that differ only in case to a case-insensitive database, the second record loaded will update the first record loaded.

  • If you select Record Load Options - Only add new records, the new records will be inserted into the table.
    • Example 1: Suppose that you use a case-sensitive database to create an unload file that has two operator records - "operator01" and "operator02". You then load this unload file into a case-insensitive database which already has an operator record "OPERATOR01". In this case, "OPERATOR01" will remain unchanged and "operator02" will be added.

      Note: If you try to load records with unique IDs that differ only in case from records that already exist in the case-insensitive database, the data in the unload will add only the records which do not yet exist in the case-insensitive database.

    • Example 2: Suppose that you use a case-sensitive database to create an unload file that has two operator records - "operator01" and "OPERATOR01". You then load this unload file into a case-insensitive database which does not have either operator record "OPERATOR01" or "operator01". In this case, "operator01" will be added but "OPERATOR01" will not be.

      Note: If you try to add two records with unique IDs that differ only in case to a case-insensitive database, the second record will not be added.

Related topics

Case-Sensitivity
JavaScript/RAD implications of a case-insensitive database environment
Oracle case-sensitivity
Service Manager Installation