[ISS Support Case] Historian Migration

Last updated: March 7th, 2025

Description

New HW/SW for 2020R2SP1P01 Historian. Cannot successfully migrate Runtime DB from Historian 2014. Before setting up a lab 2014 and upgrading to 2020R2SP1P, I would like to verify a direct import is not possible. I've run the User and NodeName scripts and they appear successful. SMC errors include invalid object names for "dbo.TagExtendedPropertyInfo" and "dbo.SearchMethodSyncRequest".

Author: Kevin Modlin
Published: March 7th, 2025

Details:

Product: Historian

Version: 2020 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	04/07/2023
Case:	84185

Give feedback about this article

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.

[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.

[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.

[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.