Echo setup and trigger‑based table synchronization between two databases

Hello,

I am new to the platform and to TMS products. I recently acquired TMS BIZ and I have a question regarding the Echo product.

I have two databases, A and B, both running on MSSQL. I need to synchronize a single table between them: all operations happen in database A (local) and must be replicated to database B (external). The applications that use these databases do not use TMS, so I will need to create a separate application, and I believe I should use the trigger‑based change tracking option — if I am correct.

The problem is that I am not sure where to start. I would like to understand how Echo creates its administrative tables, or how I should create the trigger that Echo will monitor.

Thank you in advance for your guidance.

TMS Echo will only replicate (synchronize) data that is modified by TMS Aurelius. It uses TMS Aurelius events to track the changes.

If your have applications that do not use TMS and save to those databases, such data will not be synchronized by TMS Echo.

Wagner, thank you for the feedback.

Since Echo doesn’t fit my scenario, I’ll need to implement a manual solution. I’m still learning Sparkle, RemoteDB and Aurelius, so I considered using them for a simple replication flow but I don’t yet know which is best. Could you point me in the right direction for replicating a single MSSQL table?

The more complex part is not Sparkle or Aurelius or RemoteDB, but your replication logic. You have to:

  1. Log/track all modifications made to the database
  2. Pack/save those modifications somehow, somewhere
  3. Send the modifications from the source node to the target node
  4. Apply the modifications in the target node database
  5. Handle errors and inconsistencies

If you are not using Echo, you will have to do most of the steps yourself.
The only place where Sparkle (or XData) can help you is in step 3, which is sending the data, if you prefer to use an HTTP server/client mechanism to do so.