• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 584 subscribers
  • Views 571 views
  • Users 0 members are here
Options
Related

Is there official support for storing alarms and events in a database such as MS SQL or SQLite?

Rohan Patel

Just like how Citect SCADA (Plant SCADA) stores the alarm and events to its proprietary database, is it possible to change it to MS SQL or SQLite database?

I know the alternative ways to store these to database but with that we have limitation to update alarm status during specific time only, after that it'll left with the last status it had.

Parents
  • +1

    Hi  ,

    I've seen many customers implement their own Alarm storage solutions (in addition to the built-in Alarm storage).

    Some examples:

    1. AVEVA Historian + AVEVA Plant SCADA Historian Connector to store alarm history. This alarm history can then be quiried via sql commands or oData interface.

    2. Setup directly within Plant SCADA, an Alarm device that outputs to a SQL database. See the help topic "Configure SQL Device" and "Add an alarm category" for more information on how to do this.

    3. Custom Cicode which opens the alarm event queue and stores each event in a SQL database using the SQL Cicode functions. This is more advanced and requires some engineering to implement.

    Hope this information helps.

    There might also be examples on the Knowledge Base of the above or Toolbox (https://softwareforums.aveva.com/citect_community/f/toolbox).

    Kind regards

    Olivier

  • 0 in reply to Olivier

    Hi   In 2nd & 3rd option if communication between Plant SCADA & SQL Database fails & restore after 8 hours can it backfill previous data or it only stores real time alarm, event data to sql database.  

  • 0 in reply to Sanjay Dharia

      We also looking solution of Plant SCADA Trend data logging to SQL Database located at different PC in same network without using Historian server. How can we Log Trend data to SQL Database without interruption, If communication fails for some time between Plant SCADA & SQL Database after comm restore, automatically Trend data should backfill in SQL. If we use ODBC connection then it only stores real time Data. We required continuous data logging even if communication fails & restore.  Please support, Thanks in advance  

Reply
  • 0 in reply to Sanjay Dharia

      We also looking solution of Plant SCADA Trend data logging to SQL Database located at different PC in same network without using Historian server. How can we Log Trend data to SQL Database without interruption, If communication fails for some time between Plant SCADA & SQL Database after comm restore, automatically Trend data should backfill in SQL. If we use ODBC connection then it only stores real time Data. We required continuous data logging even if communication fails & restore.  Please support, Thanks in advance  

Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.