I should also mention that there are pros and cons to migrating datasets to SPICE. While it can improve performance, it introduces a delay before updates are reflected, meaning we lose real-time visibility into the data. For this reason, we review each dataset on a case-by-case basis to determine whether migrating to SPICE is appropriate, rather than applying a one-size-fits-all approach.

What's the delay for SPICE? I know data overview does not update often (and can be annoying), but are other SPICE tables the same? 

What's the delay for SPICE? I know data overview does not update often (and can be annoying), but are other SPICE tables the same? 

The refresh frequency for SPICE datasets is configurable. In Trados, we perform a full refresh every 24 hours and an incremental refresh every 15 minutes for all of the datasets using SPICE. Assuming no issues are encountered during an incremental refresh, you should therefore only see a data synchronization delay for a maximum of 15 minutes.

Note, however, there are some other side effects of using SPICE, due to the way incremental refreshes are performed, such as the issue reported in the KB article here - - Information on the data refresh strategy used in Trados Enterprise, the root cause of discrepancies observed in Custom Reports, and a temporary workaround to ensure accurate data representation. - Knowledge Portal.

Going back to my earlier comment, we therefore decide selectively on a case-by-case basis which datasets are appropriate to move to SPICE based on various factors.

Cheers,

Ian