Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ System Platform

Upgrade from a previous version

  • Last UpdatedJan 22, 2025
  • 2 minute read

You can upgrade directly to the current version of the Historian (2023 R2 SP1) from Historian 2017 and later versions.

You should upgrade the Historian Server before upgrading Historian remote IDAS nodes. Remote IDAS nodes that are not upgraded will remain fully functional. However, it is strongly recommended that you upgrade them to Historian 2023 R2 SP1 to incorporate minor improvements and simplify further upgrades and maintenance.

If you have been using replication, when upgrading historian nodes, upgrade the tier-2 historian node first and then the tier-1 historian node.

Upgrading From a Version Earlier Than Historian 2014 R2

You must make some changes manually if you need to upgrade from a version of Historian prior to version 2014 R2. When you run the Configurator, it generates SQL scripts that you can use for manually migrating older releases.

To upgrade from an earlier version of Historian (before v.2014 R2)

  1. Install Historian 2023 R2 SP1 and run Configurator.

  2. From the Operations Control Management Console, shut down and disable Historian.

  3. Locate SQL scripts that you will need for intermediate migration in this folder:

    C:\ProgramData\ArchestrA\Historian\Install\Scripts

  4. From SQL Server Management Studio:

    1. Drop the Runtime database.

    2. Restore a backup of the Runtime from your previous version of Historian.

    3. Disable any triggers or constraints that would prevent schema changes. This prepares your database for changes.

    4. Run the scripts you need to update Historian.

  5. If you are upgrading from a much older version, you may have to run scripts to incrementally upgrade versions. Run the scripts in the order they appear (when sorted alphanumerically).

  6. Restore any changes (triggers and other constraints) that you made to settings in step 4.

  7. Shut down the old server's remote IDAS.

  8. From the new server, force an update to the remote IDAS configuration.

TitleResults for “How to create a CRG?”Also Available in