• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 1 reply
  • Subscribers 17 subscribers
  • Views 240 views
  • Users 0 members are here
Options
Related

Migrating Existing Historian Database

Nomthandazo Majozi

The customer Migrated his Historian to version 2023

Looking at the logs, I am seeing an unusual error, something SQL based.

 

The historian appears to be functioning, and pulling the data in.

But it concerns me that I am seeing these SQL messages.

He followed this Technote to Migrate   (Migrating Older Historian Runtime Database to Historian 2017, 2020 or 2023)

Parents
  • +1

    As a guess, this isn't actually related to the upgrade, but has something to do with a query that wasn't structured correctly and just became apparent after the upgrade. To help isolate the problem, use the Microsoft SQL Profiler to trace all the queries sent to the “Runtime” database and look for the errors there. It will include the query text and user context

Reply
  • +1

    As a guess, this isn't actually related to the upgrade, but has something to do with a query that wasn't structured correctly and just became apparent after the upgrade. To help isolate the problem, use the Microsoft SQL Profiler to trace all the queries sent to the “Runtime” database and look for the errors there. It will include the query text and user context

Children
No Data