I am trying to replicate two tables from host A to host B.

I have defined after insert/update triggers on these two tables tableA and tableB. I want these triggers for these two tables to be invoked during replication. Also I want tableA to be replicated first as triggers for tableB depends on data from tableA.

The replication works fine, but triggers are not invoked at all.

Please let me know the solution for this problem.

Thanks in advance
Sam

triggers are independent from replication
if an insert /update occures, the trigger should fire.
apply is executing insert-delete-update statements
if you mean after sql statements defined by replication, these are regular statements and not triggers, that fire after the apply finishes a cycle.
if you want to keep the sequence of operation as on source, there is a setting in apply - transaction based... this will respect the order

Acctually the replication uses load mechanism for tableB and import mechanism for tableA. So the trigger gets fired for tableA, but not for
tableB (because load doesn't fire trigger). However I want both triggers
to get fired and also I want to replicate tableA first and tableB first.
So that trigger for tableA fires first as trigger from tableB depends on
data from tableA.

I will appreciate if you can provide a solution for my requirement.

Thanks in advance

You should be able to put the trigger logic into a SQL stmt or a Stored Proc and run after each subscription-set processing cycle.

HTH

Sathyaram

whenever apply applies the modifications, it uses regular statements
is this the initial load ?
do the initial load manually with import and let apply keep the tables maintained