You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Replication Triggers
- Thread starter manni132s
- Start date
Dr
Hmm - replication triggers fire in order where as normal DB triggers don't always.
EG
create cust1
create cust2
A standard write trigger "may" show cust2 first.
Replication triggers are typically used to create a disaster (DR) copy of the master database.
I don't believe here is a find trigger.
You don't really need the "create" one since its immediately followed by a "write" with the initial values of the table as specified in the database schema
Hmm - replication triggers fire in order where as normal DB triggers don't always.
EG
create cust1
create cust2
A standard write trigger "may" show cust2 first.
Replication triggers are typically used to create a disaster (DR) copy of the master database.
I don't believe here is a find trigger.
You don't really need the "create" one since its immediately followed by a "write" with the initial values of the table as specified in the database schema
Hello,
We use replication trigger for three reason :
- Interface live with other software
- Save solution
- Make specific code in replication trigger so that no standard program be modified and have to be maintain with version evolution.
Hello BONO,
I was thinking implement Replication Trigger to keep a Replication Database (as Backup). Did you see a poor performance of Database after Implement Replication Triggers? We have a database 12 Gb in a Linux Server (2 Processor - 700Mhz, 2Gb Memory) - Progress 91D.
Thanks.
I was thinking implement Replication Trigger to keep a Replication Database (as Backup).
Use AI (After Imaging) for that.