Hello network,

I am currently logging alarms to an SQL database using the logging feature by creating a database segment. However, I noticed that the alarm timestamps (dates) are not appearing in the corresponding SQL table.

Could you please guide me on the simplest and most efficient way to archive alarms for a period of one year in a format that is easily readable for the customer, such as a CSV file? Any recommendations or best practices for achieving this would be greatly appreciated.

------------------------------------------------------------------------------------------
Split from WinCC Professional Alarm Logs.

Hi,

You can use the "Alarm view" control in Runtime to display Logged alarms and export them to a CSV file using the control's integrated button.

Configuring an alarm view for logged alarms

Hi again,

I believe that through the Alarm Control, it will be possible to export a maximum of 1000 in 1000 rows manually, since although it is not what really exists in the log file, it is the maximum that the Alarm Control can show (performance and system behavior), as shown here:

Why are only 1000 messages shown in the archive window although there are more in the archive?

As Murof said, if you want to access more alarms for export, you would have to access the database directly. And ,as the database is encrypted for security reasons, you would need the Connectivity Pack option (already included in WinCC Professional).

Dear Murof,

Thank you for replying. You have suggested to use OLEDB Provider. Normally we can connect to WinCC Database using ADODB by activating Data Source Administrator(ODBC) . Can I also reach my archieve alarms same way?

Also could you please explein diffrences of OLEDB and ADODB ? Which way is more useful for my application?

Thank You