Manually purge and archive the database

You can purge and archive your alarm database manually. This overrides the activation time and starts the purging and archiving immediately.

The purge operation checks for the presence of an archive file and appends to the same. If the archive file is not present, the file is created as per the naming convention and then used for archiving.

The purge operation does not delete entries in tables such as ProviderSession, Query, and Cause that are linked to the main tables such as AlarmMaster through foreign key constraints. The related records in these tables are written to the files to maintain the data consistency and also retained in the database.

Caution: Manually purge all records (the Purge All Now option) only when the Alarm DB Logger service is stopped. If the purge operation is committed successfully while the Alarm DB Logger service is running, the Alarm DB Logger service stops logging and starts caching records.

Manually purge and archive records from the alarm database

1. Open the Alarm DB Purge-Archive utility. Do the following:

   1. In the Tools view, expand Applications.

   2. Double-click Alarm DB Purge-Archive.

2. Select the Purge/Archive tab.

   

3. Select Test Now to perform a test purge to verify your connection to the database and archive locations.

   The test purge creates empty archive files in the specified archive folder. The Status area shows a message that the test was successful.

   

   The Test Now button is available only if you have chosen to archive your purged records. The Archive option is located on the General tab.

4. Purge the records from the database. Do either of the following:

   • Select Purge Now to purge the selected records.

   • Select Purge All Now to purge all records.

5. To stop a purge, select Cancel Purge. If you cancel the purge, the alarm database is rolled back to its original state.