The main tables used to track item updates to the index volume are the Vault Store database JournalUpdate table and ItemUpdateStatusLog table.
This table contains information about items that have been updated in the archive. This includes when items have been moved to a different folder in the archive or the retention category has changed. If the item update has not been sent for updating in the index, the IndexCommited flag is set to 0. Conversely, if the item has been sent for updating in the index or the update will be ignored as a future update exists for the same item, then the IndexCommited flag is set to 1.
Run the following SQL Query to identify the items within the JournalUpdate table where indexing has not been attempted yet.
WHERE IndexCommited = 0
Note: Replace <VaultStoreDBName> with the name of the current Vault Store database name.
This table contains records for items that are currently being updated in the index. Successfully updated items are removed from the table. If there are items that have failed to be updated in the index, these will remain in the ItemUpdateStatusLog table. These items will remain in a failed state until a subsequent update of the same item succeeds, the item is deleted or the index volume is rebuilt.
Only when an item update has been successfully indexed, will the update be visible in EV Search results. Therefore searching the archive for items that have not successfully been updated will only return results if the original item attributes are used. Using the updated attributes will not return the item. For example, if an item was archived and indexed in Folder1 and then moved to Folder2, until the update is fully processed, only searching in Folder1 would find the item, searching Folder2 would return no results. There might be a slight delay between the item update being acknowledged (and therefore searchable) and the item being removed from the ItemUpdateStatusLog.