The main SQL tables used to track the archival of data and the addition to the index volumes are the Vault Store database JournalArchive table and ItemAdditionStatusLog table.
This table contains information about items that have been archived. If the item has not yet been sent for indexing, the IndexCommited flag is set to 0. Conversely, if the item has been sent for indexing and has been acknowledged by the indexing engine, then the IndexCommited flag is set to 1. When this flag is set to 1, the item could either have been successfully indexed or could have failed to be indexed.
Run the following SQL Query to identify the items within the JournalArchive 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 added to the index. Successfully indexed items are removed from the table, except those that have missing content, which remain in the ItemAdditionStatusLog with the missing content reason stated in the ErrorNumber column. If there are items that have failed to be indexed, these will remain in the ItemAdditionStatusLog, until a subsequent retry is successful. After two further failed retry attempts, the poison pilled flag for the item will be set and the item will no longer be retried. Poison pilled additions will be retained in this table and will be retried when the index is repaired or rebuilt.
Only when items have been successfully added to the index, will they appear in EV Search results. Due to the asynchronous nature of the 64bit indexing engine, an item can appear any time after it has been submitted to the indexing engine. There can also be a slight delay between the item being acknowledged (and therefore searchable) and the item being removed from the ItemAdditionStatusLog.