At 12:38 AM 22/06/2005 +0200, Milan B. wrote:

>There is a third approach, similar to what you wrote here: use triggers
>and events. You can have replicator sitting in background (on main
>server) and waiting for event, when event fires, it would just read from
>transaction_log table (filled by triggers) do a query with WHERE clause
>using the PK, and insert/update/delete that record in other database.
>
>It is very good approach. If network gets down, replicator can build a
>list of events, and when connection is back online it can update the
>other database. Since it is only using PKs it is not performance
>intensive at all. It is somewhat invasive on database structure but if
>proper naming is used for all triggers, then it is probably not an issue.
>
>Now, the thing is: I don't know if such replicator exists. I'm even
>considering to make one myself, but why waste time if there is something
>already there. Do anyone know about such replicator?

Yup. That's exactly how the IBO one-way replication works.

Helen