Archive and Prune Alarm Journal for Auditing

Ignition
1

We have recently rolled out Ignition in our facility. I'm now seeing that our AlarmJournal query is taking a long time to complete and I'm seeing errors on the gateway.

We currently have about 1 years worth of alarms stored and require to maintain a total of 7 years worth for auditing.

Does anyone have a solution where we are able to maintain ~6 months live available through ignition and once the data is older than that export it to another database to maintain the 7 years worth of cold data.

similar to the prune feature, but rather than deleting, Exporting.

2

Well I did some more thinking in the past 5 minutes...
I don't see why I couldn't set up two alarm journal profiles, one with the prune age set to 6 months the other with its prune age set to 7 years.

Then only reference the 6 month journal in the app

3

You should probably also have a database administrator examine your instance for tuning and query analysis. You probably need more careful indexing.