Re: Middleware --- polling or triggering

Ken
\
Not too sure how you're going to get the trigger approach to work without a DB link.

Otherwise, there are a number of approaches that can be taken. A lot of companies are now starting to concentrate on this area, including Oracle. As a matter of fact, the group I work with in Oracle Consulting specializes in just this area. Some places to look:

1. Check out the Enterprise Application Integration space. For example, look at http://www.messageq.com. Mostly, this stuff is looking at disparate systems (DB2 to Oracle, for example) using message brokers and the like.
2. Alternatively, it sounds like you're looking at an Oracle to Oracle connection. If that's so, you can use things like
   1. automated batch transfers using export/ftp/import
   2. Advanced QUeuing in Oracle8, using triggers to queue messages from one database to another either via a db link or via flat files
   3. look at Mercator or STC's Datagate product for transformation engines

etc. etc.

Let me know if you need more details.

Pete

Ken wrote:

> Hi there,
>
> I am studying which way is the best to refresh the DB.
> There are two DB and let say A and B, they are in
> different machine. When the update is done on A,
> then we need to refresh the corresponding table
> in B. Now let's assumed that the db_link can't be used.
> we are just thinking of two approaches
>
> 1. to set the timer in middleware to periodically do the
> synchronisation between the two DB.
> 2. to setup the trigger in DB A, any update in A will be
> firing a trigger to update B.
>
> Is there any whitepaper or document in comparing this
> two approach ? Should you have any other alternatives,
> kindly drop a few words also, many thanks.
>
> Ken

Received on Tue Aug 31 1999 - 14:52:33 CDT