Update an existing MES database

Use the Configurator Database Setup component to update an existing MES database, including upgrading the database to a new version:

• Migrate the existing database to the new MES version.

• Overwrite the existing database with a new MES database.

  Note: Ensure that all active connections to the target MES database are closed prior to configuring the existing MES database, including any scripts running against the database. Verify whether existing connections are active using the Operations Control Management Console (OCMC) Log Viewer.

• Keep the existing MES database.

Update an existing MES database

1. Complete the database server and MES database name settings:

   Server Name

   The name of the server that is hosting the existing MES database. The server name defaults to the local server. Supported server names include IP names (IPv4 and IPv6), SQL server named instance conventions, cluster names, and SQL Server Availability Groups.

   When using a Failover or Availability Group naming convention, the configuration must be performed when the primary node is active.

   Database Name

   The name of the existing MES database. The name defaults to the existing database, if one is found.

2. Review the user account used to access SQL Server.

   For the Database Setup component, the user account provided must have adequate rights on SQL Server to create a database. For more information, see Specify SQL Server user authentication.

3. Select Validate to check that the user account you have specified can access the specified SQL server and MES database.

   As part of the validation, as estimate is calculated for how long upgrading the existing database will take. If the estimate is more than 10 minutes, the estimated time is displayed in a message box.

   

   If the validation is successful, the Existing Database settings appear.

   

   If the specified database is not found, then the settings for creating a new database appear. Try entering the correct name for the existing database and clicking the Validate button again.

4. Do one of the following:

   • To migrate the existing database to the new release, select Overwrite and and ensure Migrate data checkbox is selected. Then go to step 6.

   • To overwrite the existing database with a new MES database, select Overwrite but unselect the Migrate data checkbox. Then go to step 5.

     When Overwrite is selected and the Migrate data checkbox is unselected, the Advanced settings properties are enabled.

   Note: If you choose to overwrite or migrate the existing MES database, it is strongly recommended that you back up the existing database before proceeding in case you need to recover its content. If the migration process fails, you will need to restore the original database and fix any errors to try again.You can back up the database from SQL Server Management Studio.

   • To keep the existing database, select Keep. Then go to step 6.

     When Keep is selected, no changes are made to the existing MES database.

     

5. (Optional) To set the Path, Initial Size, or Percent Growth of the new MES database data file or log file, expand the Advanced settings and enter values in the fields. Then go to step 6.

   

   Path

   The path of the data or log file.

   Initial Size

   The initial size, in MB, of the data or log file.

   Percent growth

   The percent by which to limit the percent growth of the data or log file.

6. If the existing MES database that you are migrating has the system parameters for recording distinct production records set but instead you want to aggregate these records into hourly records and disable distinct production records, select the Aggregate existing item production records option.

   If the existing MES database already has the system parameters for recording distinct production records set to False, then the setting of this option has no effect.

   It is recommended to aggregate production records into hourly buckets, as this will improve the overall system performance for recording production and reporting on production data. In versions prior to MES version 4.5, recording distinct production records was required for reporting hourly KPIs, but this is no longer the case. You might still want distinct production records for other reasons, in which case do not select this option.

7. To update the existing MES database, select Configure.

   CAUTION: While the database is being migrated from a prior version, the Configurator application cannot be closed or switched to a different component's configuration. If the Configurator application is stopped prematurely (such as closing the application or shutting down the computer), the MES database will be in an inconsistent state and might not function correctly.

   The SQL scripts that migrate or create the database run. A message appears, asking to wait while the database configuration is performed.

   

   Progress information and any error messages appear in the Configuration Messages box.

   If the database migration or creation completes successfully, a success message appears in the Configuration Messages box. Also, the MES Database Setup status indicator changes to a green check mark.

During migration, if the database is configured to use OS Group security and does not already have the OS Group SIDs in the MES database, the configure operation will attempt to create them. If the domain is not available, then use the OS Group SID Utility to update them later when the domain is available. See Importing Windows Active Directory Group SIDs into the MES Database.

If migrating from MES 2014 R3 (version 5.3) or earlier, the migration process creates new tables for tracking utilization data and moves the existing data into these new tables. The original tables still remain in the database but have been renamed to util_log_deprecated, job_util_log_link_deprecated, and tpm_stat_deprecated. These deprecated tables can be deleted once the migration is deemed to have completed successfully. New views are created with the original table names of util_log, job_util_log_link, and tpm_stat to ensure any existing queries or reports continue to function after migration.