Shared Variable Engine - Citadel

[Joachim082]

We are logging shared variables with the citadel database via the variable logging. In some cases (reset of PC ...) citadel makes a repair of the database after restart. When having databases greater than 20-30 GB this operation takes at least one hour. During this operation the Shared Variable Engine is not responding. When using the shared variables not only for logging purpose but also for controlling options and visualizations on that same pc this is very critical - this stops also the production for one hour.

It will be better to activate the Shared Variable Engine although during the repairing process of the database. We could pass on the data during the logging process but not on the controlling part of that aggregate.

Best Regards,

--

Joachim

[hewu]

Great Idea! I like it.

[Woss]

This is more than necessary.. The fact that the whole system stops during citadel repairing is a very annoying bug

[JKSH]

While this doesn't directly address your request about the SVE, NI does recommend that you don't allow your "live" database to grow too large: http://www.ni.com/white-paper/6579/en/

"Plan for regular archiving operations to reduce the amount of data stored in the operational database. To achieve maximum performance, you might want to store only the last 1GB worth of data in the operational database. The actual amount of data you decide to keep in your operational database depends on the application."