Re: No future for DB2

"Noons" <wizofoz2k_at_yahoo.com.au> wrote in message news:42f14d48$0$11928$5a62ac22_at_per-qv1-newsreader-01.iinet.net.au...
> Madison Pruet apparently said,on my timestamp of 4/08/2005 6:07 AM:
>
> >>So, what happens if a trigger in that table changes ANOTHER
> >>table that is not being replicated? Do the OTHER table's
> >>changes get replicated as well? Note: you asked for "ALL trigger
> > activity".
> >
> > At a minimun the replication solution should be able to either prevent
> > triggers from firing on the target if it is populated by a replication
> > apply, with the assumption (and policing) that all of the tables
associated
> > with original transaction is replicated as part of that transaction.
>
> I was not talking about triggers on the target nor were you. It's very
> clear above. Don't change the subject.
>
>
> Fantastic. I couldn't care less about the "or" bits to "deal with this
> problem". First of all, you didn't even understand the problem.
> the original table". That's : *ALL* OF THE TRIGGER ACTIVITY PERFORMED
> ON THE *ORIGINAL TABLE*. That is a much more complex requirement.
> I want to know how YOU address it with specific NATIVE Informix
> replication (or any other product's for that matter).
>

Fair enough --- on the IDS informix server, to do this with say 5 instances by issueing the two commands

cdr define template noons --database=noons --master=node1 --all cdr realize template noons --syncdatasource=node1 node2 node3 node4 node5

This would set up an update anywhere of everything in the noons database using the five servers. Received on Wed Aug 03 2005 - 18:21:46 CDT