Limit Processing Load on Server During Migration

Both data migration utilities provide you with the ability to limit the amount of processing load on the server during migration. This allows your online Historian Server to continue processing data efficiently while migration occurs. By modifying the Events rate/second field in the Classic Historian Migration Options window or the Max values/sec field in the Advanced Historian to Historian Migration Utility, you can specify how much data is sent and therefore how much processing power the Migration Utility receives on your system. The minimum you can set this rate to is 10,000 (or 0, meaning no throttle); the maximum you can set this field to is 100,000.

If you are performing a migration on a computer that is also processing other data or applications, you may want to set the event processing speed lower to allow your other applications to process well. The Historian Classic Migration and Advanced Historian Migration defaults to 10,000 events per second. The default value allows you to throttle back the Migration Utility to allow for other applications processing, as well as continue running your Migration Utility at a reduced speed. If you are not running other data or applications on your machine and you want to run the Migration Utility at maximum speed, set the Events rate/second or Max Values/sec fields to 0.

Tip: It is recommended that you do not set the events per second past 25,000 or below 10,000 (unless to 0). The higher the events per second, the faster your Migration Utility processes the migration. For example, the migration may take twice as long at 10,000 as it will at 20,000 but it will take less CPU time.

Note: You cannot change this entry while migrating. It must be set prior to or changed after migration.