Investigate more efficient retrieval from and clearing of EAI table
Matthew Clark 10 years ago in UNIFYBroker/Frontier ichris/chris21 • updated by anonymous 8 years ago • 2
At SSICT, a large initial export of 52000 updates to the DET table caused the EAI changes table to contain a similar amount of changes. This resulted in the Import Changes operation for the connector taking 9-10 hours to execute, and the EAI table for the DET form was not cleared. It was worked around by forcing a deletion of the CHEAI file following the initial load exercise. Investigate any improvements that can be made to this interface for environments where extremely large numbers of changes can take place.
Customer support service by UserEcho
Unsure what could be done here - it would depend on if an alternative change detection mechanism could be found instead.
Marked as Unassigned.
Migrated to VSO.