Definitely use ER and not re-invent the wheel using old trigger technology!
Andr' D.
>From: St'phane Gadoury<stephane.gadoury@transat.com>
>To: <informix-list@iiug.org>
>Subject: Replication VS Triggers
>Date: Wed, 23 Jun 2004 09:55:58 -0400
>
>Hi list,
>
>I need to replicated a subset of about 15 tables from IDS V7 towards a SQL
>Server. In that table count, I have 3 tables that are always in the top 10
>in terms IO, during the day.
>
>I have 2 differents set up, which I could used.
>
>1- Set up triggers on the required tables
>2- Set up ER for those tables towards another instance
>
>My concern is mainly performance and ease of management (since the data
>will
>go populate the sqlserver DB). I would tend to think that setting up 15
>triggers with all of them triggering on insert, delete and update would be
>"heavier" on the performance compare to seting up those tables with ER and
>having replication being set in one direction.
>
>Also, since the data would be used to populate the sqlserver, the
>replication would be easier to manage in case of a crash or any other
>failures.
>
>As usual, comments &/or suggestions are welcome.
>
>Thks !
>
>St'phane
>
>
>
>
>
sending to informix-list