Alarming and Event Data Storage Locations

[Davidd]

I'm having a problem where the Alarms and Events files are filling up the system disk and causing Lookout to crash.  Is there any way I can set things up so that those files are stored on another disk?  I already have the Historical files being archived on a separate disk, but the alarms and events seem to have stayed on the System disk.  The system disk doesn't have that much free space all the time, which is why I put the historical files somewhere else.

Also, I have the Historical Data system set to only archive data for 90 days (it was changed a while back from storing perpetually), but I still have files in the database going back years.  Is there a way to purge the old data out?

David Dudley

[Paul M.]

David,

It's important to note the alarms and events are actually in a separate database from Citadel. 

This KnowledgeBase article discusses removing/archiving alarms from the database:
http://digital.ni.com/public.nsf/websearch/B23BDD585BAEB25086256C00005C2851?OpenDocument

Moving the alarms database is a bit more tricky.  It uses the MSDE 2000 SQL engine, which defaults to using a database on the drive it gets installed to.  I think short of installing Lookout to another drive, there's no "easy" way to move it over.

Message Edited by Paul M. on 04-08-2006 12:16 AM

[Davidd]

Should have also said that we're using Lookout 5.1, which I understand uses a different database system. Does that make a difference?

[Davidd]

Is there a way to have davta automatically deleted from this database?  I don't need historical alarms 4 or 5 years old.  Just clutters things up.

David Dudley