[ISS Support Case] Historian Migration Information Request.
Last updated: March 7th, 2025Description
Im working on a historian migration from 2017 U2 to 2023 P02. A few questions: I seem to recall a tech note or instructions on how to move over the DB from SQL to keep all the configurations intact, but I cannot locate it in my archives nor find it at AVEVA or InSource. Do you recall something like that, can you put hands on it, and can you get me a copy? Are there any other pitfalls/support docs I should know about? Are there any special install instructions when installing Historian client on a true Terminal Server?
- Author: Kevin Modlin
- Published: March 7th, 2025
Details:
Product: Historian |
Version: 2017 |
Solution: [Solution is visible below when you're logged in and have a current subscription] |
Date Created: | 09/13/2023 |
Case: | 85309 |
Recommended articles
[ISS Support Case] Historian loses connection after shutting down
If the historian is shut down and disabled then re-enabled it doesn't connect to tags that haven't changed. Reboot re-establishes connection.
Read More[ISS Support Case] Trying to access old history blocks
They have a very old system they're trying to open a trend or see the data, but they don't see a trend program and can't figure out how to open the file. They believe they have the data, but it's running in demo mode and won't show data. This is an offline PC and they want to avoid putting it online, so we can't do a screen share.
Read More[ISS Support Case] Trend SQL Login Failure
Client reached out due to receiving time out error message when logging into SQL to View Trends remotely on Development node.
Read More[ISS Support Case] Wanting to pull 9 months of historized data
-Customer is wanting Historized data from the last 9 months in a .CSV file. Or in SQL. and wants to know the best practices.
Read More