Which elements upgrade and when does upgrading occur?

Project configuration

The project configuration includes the Studio project and settings. The upgrade procedure occurs when the service starts. Upgrading the project configuration includes:

• Configuration database schema

  Important: If you add additional permissions to the configuration database, you need to manually add them back when you upgrade to later versions.

• Studio items and their properties

• Authstore and security settings

State database

The upgrade procedure occurs when the service starts. Upgrading the state database includes:

• Master Data Management (MDM) settings

• Historical caches

• Metrics Calculation Queues

SQL Data Repository

The upgrade of the SQL Data Repository is dependent on the AutoUpgrade setting of the Data Repository item in Studio.

• True - This means the data repository schema attempts to upgrade automatically when the item starts. This is the default setting.

• False - This means you must use the Initialize Database command to manually control when the upgrade procedure occurs. This is the recommended setting.

  Note: In a production environment, we recommend that you set the AutoUpgrade property to False, so that you can manage when the database upgrade occurs. On a large database, upgrading the database schema can be time consuming and requires care.

Which elements do not upgrade?

Important: Make backups of these items before you begin the upgrade process.

The following elements are not updated during the AVEVA Production Management upgrade process. Examine these items and make manual changes to enable successful integration with the upgraded software.

• Code items - Code items can be affected by changes in the upgraded software. You may have to manually update your code items to reflect the latest version of AVEVA Production Management.

• Reports - Reports can be affected by changes in the upgraded software. You may have to manually update your reports to interact with the latest version of AVEVA Production Management.

• Dashboards - Reinstall and configure dashboards into the newly upgraded environment.

• CLR Stored Procedure - Reinstall the CLR Stored Procedure into your upgraded environment.

  If you are using a remote data repository, you need to manually install the CLR Stored Procedure. This takes care of the need for the service to share DLLs with SQL Server when creating a new project.

  For detailed installation steps, refer to Install the CLR Stored Procedure in the Administrator (Studio) online help.

• Configuration files - Configuration files are not modified during the upgrade process. Instead, they are overwritten by new versions of the configuration files and your existing configuration settings are not saved.

The new configuration files can contain new properties and new default settings that you may want to use. Therefore, to preserve your previous settings and take advantage of new properties/settings, you can do a compare and merge. Pay attention to these configuration files:

• SE.SPO.AmplaService.exe.config - Contains settings for the service.

• SE.SPO.AmplaStudio.exe.config - Contains settings for Studio.

• Web.config - Contains settings for web services.