Migrating data log models to DataLogPro
Migrate the legacy data log models to DataLogPro to take advantage of the DataLogPro functions and centralize the historical data in InfluxDB. The migration essentially means migrating the list of tags in the data log model to DataLogPro and these tags' historical data to InfluxDB. You can only migrate historical data stored in file sets or SQL Server.
To migrate the list of tags in the data log model to DataLogPro, you can add them one by one in DataLogPro or use a CSV file to add a number of tags at once. To migrate the tags' historical data to InfluxDB, the operations vary depending on whether the historical data is stored in file sets or SQL Server. However, unlike migrating historical data in file sets, which is supported by FactoryTalk View Studio's built-in function, migrating data in SQL Server requires knowledge of database schemas and Influx language programming.
To migrate historical data in file sets:
To migrate historical data in SQL Server:
Remarks
- When migrating historical data from data log models to DataLogPro:
- New tags' historical data will be added to the InfluxDB database.
- If the same tags already exist in DataLogPro or were firstly merged into the InfluxDB database during an earlier migration, their historical data will be merged.For example, if a tag's previous logging frequency is every 10 seconds, and the logging frequency of the same tag to be migrated is every 5 seconds, these additional logging data will be merged.
- If your application is a network distributed application, and you are logging to a local InfluxDB database, the historical data will be migrated to the active HMI server only. You must manually migrate the historical data to the standby HMI server by first switching to the standby HMI server, and then migrating the data to that server.
Provide Feedback