Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

Set a remote IDAS to "classic"

  • Last UpdatedFeb 27, 2025
  • 1 minute read

When the Historian Server is upgraded from a prior version, all existing remote IDASes are set to "Classic". (That is, Classic = 1 in the _IODriver table).

If a remote IDAS is added after installation, it is created as a new IDAS. But if it is used for data exchange with a legacy system, it should be explicitly set to "Classic".

To set a remote IDAS to "Classic"

  1. In SQL Server Management Studio, type this query:

    Select * from _IODriver

  2. This lists each IDAS on the computer. Notice that Classic IDAS shows "0" in the Classic column.

  3. To change a Classic IDAS to a New IDAS, type this query (where the _IODriverKey is the unique key for the IDAS you want to change):

    Update _IODriver

    SET

          Classic = 1

          WHERE _IODriverKey = 3

If the legacy remote IDAS is later upgraded to Historian 2017, you can run a similar Transact-SQL script, but with "SET Classic = 0" to indicate that the IDAS is no longer part of a legacy system.

Related Links
TitleResults for “How to create a CRG?”Also Available in