CitadelControl object

[Mario_Fanelli]

Hi folks,

I want introduce in my Lookout (now 6.1) application, the possibility to perform periodically a backup of the default historical database to another on the same PC, in this way I can set the default database lifetime to few days instead of 1 year. This because I've an huge amount of data logging (up to 1000 alarms conditions and 100 trace of process variables) to the historical database, and I don't want the database size rises too much.

For doing this, I made a test application for testing the CItadelControl object. All works fine for the traces, but not for the alarms.

Is this a limitation for the CitadelControl object? If so, there's another way for making a backup of the alarms?

Thanks.

Mario Fanelli

[Ryan.S · Accepted solution]

It's a limitation for the CitadelControl object.

The way to archive alarms is to use the MAX(Measurement Automation Expolorer). Right click on database, and select Archive. It will archive both data and alarms.

The alarm data is managed by SQL Server. The file is mssql.* in database folder. If the SQL file is just around 100M after months, it doesn't matter.

[Mario_Fanelli]

Thanks Ryan,

It's possible use the sql object inside lookout to perform the copy of the alarms part of the database?

[Mike@Forshock]

Would be difficult, but not impossible.  The alarms and events are stored in 2 seperate tables inside of the SQL Server.  They have multiple relations to create the ack, unacked, cleared, uncleared, etc.  

Load SQL Server Management Tools and you can view them and create the necessary SQL code.

Not too helpful, sorry, but gives you an idea.

Mike

[Mario_Fanelli]

Thank you Mike,

I'll try it in the next days.

Bye

[Mike@Forshock]

Just a note,

We have a system with approx. 1500 logged points over 7 years and the database is about 8GB in size, so unless you have a very weird setup (SSD under 16GB) you will not running out of space any time soon.

Mike