About database migration

The data in an existing Runtime database can be migrated to a new Runtime database. The old Runtime database is not deleted. Keep the old database until the Historian migration is validated.

Important: Back up the Runtime database before performing the migration.

There is no migration for the content of the Holding database, because this database is used only to temporarily hold data when importing an InTouch data dictionary.

Any configuration data associated with obsolete system tags is not migrated.

For the event subsystem, all SQL-based detectors and actions are migrated to the OLE DB syntax. If you have any custom SQL-based detectors or actions, you need to rewrite them using the OLE DB syntax.

History data that is stored in SQL Server tables (not history blocks) can be migrated after the general upgrade has been performed.

The scripts are created when you first run the database setup utility so that you can run them at any time. The file path is:

To migrate your database

1. On a new Historian server, use SQL Management Studio to:

   1. Delete any empty Runtime database that was created as part of the installation.

   2. Restore the old Runtime database from a backup.

2. Run the Configurator.

3. In the left pane, select Historian and then select Server.

4. Configure the server. For more information, see Server configuration details, as described in Configure AVEVA Historian.