It may also be merged remotely at the daemon, using the REMOTE MERGE command. The Global daemon detects that the database involved is the location's own transaction database. The daemon will close the transaction database before the merge, and re-open it afterwards.

However, the REMOTE MERGE command cannot be used when the transaction database is full, since this command cannot be recorded properly. In this case, it may be necessary to merge it by reconfiguring. To manage the transaction dB efficiently TRINCOs (and their child elements) need to be deleted at regular intervals. Only completed transactions should be deleted. It only makes sense to merge the transaction dB after TRINCOs have been deleted, otherwise the dB will not be compacted.