JournalArchive table has grown significantly since upgrading to Enterprise Vault (EV) 8.x or later.

Article: 100020143
Last Published: 2014-09-15
Ratings: 1 0
Product(s): Enterprise Vault

Problem

Enterprise Vault 8 introduced a new feature called Transaction history. The Transaction history is used to determine how long to record updates to archives. Updates include adding new items, deleting items and moving items. The update records significantly improve the performance of vault cache synchronization by providing records of the changes to an archive since the last vault cache synchronization. If a user has not synchronized their vault cache within the transaction history period, then Enterprise Vault will process the archive to determine the updates. 

The transactions are tracked in the JournalArchive, JournalDelete and JournalUpdate tables which are located in the Vault Store databases.  Since the tables will grow larger than they did in previous versions of Enterprise Vault, additional considerations should given to ensure the SQL server does not run out of disk space. Alternatively, the number of days the Transaction history is retained may be modified. 

Solution

Follow these steps to modify this setting:
  1. Select the Advanced tab.
  2. Select Storage under List settings from.
  3. Select Transaction history from the list and click on Modify.
  4. Specify the number of days to retain updates to archives. By default, the data is retained for 32 days:

 
Note:  With the introduction of additional Enterprise Vault databases and increased database sizes described in this article, it is imperative that routine SQL maintenance is performed in addition to backups.  Refer to article 000040169.

Was this content helpful?