Upgrade from a previous version to MES 2023 R2

Upgrading from the following MES versions is supported:

• 4.0 (all service packs and patches)

• 4.5 (including P1)

• 5.0 (including SP1 and R2)

• 5.3

• 6.0 (including R2)

• 6.2

• 7.0

To upgrade from an earlier version, you must first uninstall the previous version and then install the new version.

Database migration

• If an existing database has custom indexes or keys that reference MES core tables, the database migration will fail. Prior to upgrading, drop any custom indexes and keys. They can be added back after the database migration is complete.

• The MES Database Setup component in the post-install Configurator application supports migration of databases from version 4.0 and later. To migrate from versions earlier than 4.0, you must first update the database to version 4.0. Custom modifications to any version of the MES database might not be supported by the utility and might prevent migration.

• The MES database upgrade from versions prior to 6.0 will take significantly longer than previous upgrades as the utilization data must be migrated to the new schema. Databases with multiple millions of records in the Util_Log, Job_Util_Log_Link, and Item_Prod tables will take on the order of hours to migrate. Prior to migration, the post-install Configurator application will provide a rough estimate of the time required.

• The current database structure has views that include the same columns as the tables prior to MES version 6.0 so that legacy queries will not break. However, the data will be slightly different as there are no longer extra records during shift changes.

• Starting with MES 2020 (version 6.2), an additional link table is included and the views are updated to use this new table. The migration populates this new link table, so migrations from 6.0 and 6.1 to version 7.0 also take significant time.

• Migration of MES 2020 or earlier versions will move all Data_Log_16 and Data_log_48 table data to the Data_Log table. If you previously ran the optional scripts from MES 2020 to copy the data to this new table, then you should delete the duplicate data from the Data_log_16 and Data_log_48 tables prior to upgrading so that there isn't duplicate data in the Data_Log table after migration.

• Migration of MES 2020 or earlier versions will not include any shift exception definitions as the approach for defining these has changed. Migration of shift schedules should be reviewed in close detail. You should determine whether or not a better approach exists with the new functionality added in MES 2023 for shift patterns with effectivity dates and entity-specific shift exceptions.

• Migration of MES 2023 or earlier versions will require that no other connections are active against the MES database as the migration enables read committed snapshot isolation on the database.

  Note: You can only perform a database Restore from an archive that was created with the version of MES that you are currently running. Restores using an archive from a previous version of MES are not supported and might fail.

For more information on upgrading, see the MES Installation Guide and online help.