Subject | RE: [ib-support] Re: Trigger propagation across databases |
---|---|
Author | Thomas Steinmaurer |
Post date | 2002-04-26T13:25:18Z |
Hello,
[snip]
timeconsuming, when doing this manually. IB LogManager 2.0 can help
you here in a very easy way. It's probably worth to look at ;-).
http://www.iblogmanager.com
Regards,
Thomas Steinmaurer
http://www.iblogmanager.com
[snip]
> Then create triggers on all table inserts, deletes, and updates increating and maintaining such logging triggers can be error-prone and
> order to log the primary key and action to a log table. Now that you
> know what records have changed, it's simple to replicate accordingly
> via your own replication manager which handles the updating of the
> databases involved.
timeconsuming, when doing this manually. IB LogManager 2.0 can help
you here in a very easy way. It's probably worth to look at ;-).
http://www.iblogmanager.com
Regards,
Thomas Steinmaurer
http://www.iblogmanager.com