[ISS Support Case] Database migration Upgrading Historian
Last updated: October 17th, 2025Description
Have upgraded a Wonderware Backup Local Historian server from Wonderware 2014 R2 SP1 to SystemPlatform 2020 R2 SP1. Would like to migrate the Runtime db on the Backup Local Historian from SQL Server 2012 to SQL Express 2017. Using the Database Migration steps as recommended on page 145 of the Install Guide. Made a backup of the SQL Server 2012 Runtime db and successfully restored the db into SQL Express 2017. Got to step 3, but then encountered the error message in the attached file. Logged on as a local admin on the server and can write to the destination data path folder. So, Im not exactly sure why Im getting the error message or the best option to proceed.
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
Product: Historian |
Version: 2020 R2 |
Solution: [Solution is visible below when you're logged in and have a current subscription] |
Date Created: | 09/12/2022 |
Case: | 82487 |
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