Workflow for Migrating Alarms and Events Data

If the alarms and events data is currently in Microsoft SQL 2008 or later:
  1. Install the following components on the target machine in the given sequence:
    1. Historian
    2. Alarms and Events
    3. Collectors
    4. Client Tools
    5. Standalone Help
  2. Back up the alarms and events data.
  3. Install Microsoft SQL on the target machine. Refer to Software Requirements for a list of supported versions.
  4. Restore the data that you have backed up to Microsoft SQL.
  5. As needed, perform calculations on the migrated data. Ideally, you must create an archive already to store the calculated data. For unsolicited calculation tags, migration of data will cause the calculation to be triggered automatically for the time associated with the migrated data points. Archives will potentially grow beyond the configured default size. To avoid this issue, adjust the value for the DataIsReadOnlyAfter field on the Security section of the Data Store Maintenance page of Historian Administrator (or the ActiveHours property) so that the value is large enough to contain the calculated data. By default, this value is 1 month.
If the alarms and events data is currently in a version earlier than Microsoft SQL 2008:
  1. Using Microsoft SQL Server Management Studio, back up the alarms and events data. If the database is large, consider taking a partial backup instead of a full backup.
  2. Install Microsoft SQL Server 2008 on the target machine.
  3. Restore the data that you have backed up in step 1.
  4. In Microsoft SQL Server Management Studio, under Databases, right-click the database that you have restored, and then select Properties > Options.
  5. In the Compatibility level field, select SQL Server 2008.
  6. Install the following components on the target machine in the given sequence:
    1. Historian
    2. Alarms and Events
    3. Collectors
    4. Client Tools
    5. Standalone Help
  7. Back up the alarms and events data that you have restored in step 3.
  8. Install a supported version of Microsoft SQL on the target machine. Refer to Software Requirements for a list of supported versions.
  9. Restore the data that you have backed up in step 7 to Microsoft SQL.
  10. As needed, perform calculations on the migrated data. Ideally, you must create an archive already to store the calculated data. For unsolicited calculation tags, migration of data will cause the calculation to be triggered automatically for the time associated with the migrated data points. Archives will potentially grow beyond the configured default size. To avoid this issue, adjust the value for the DataIsReadOnlyAfter field on the Security section of the Data Store Maintenance page of Historian Administrator (or the ActiveHours property) so that the value is large enough to contain the calculated data. By default, this value is 1 month.