Subject | Re: [ib-support] Replication (more) |
---|---|
Author | Paul Schmidt |
Post date | 2001-03-05T19:51:49Z |
Fabrice:
You don't want to go there. Cross engine replication always means
that one database or the other is wrong, and 99% of the time, it's
both. You will spend anywhere from 10 to 100 times as much time and
money on this, then it's worth.
The key is black-box integration, the customer can run every other
piece of software he owns on Oracle, your application runs on IB, so
you stick a box running IB in his server rack, it's only the
interface to the outside world, that you need to deal with, and that
is at the application level, not the DB level.
Most companies are not religious about the technology they use, just
if they spent a gazillion marks on Oracle, they don't want to throw
that away on another technology. However they could be perfectly
happy will multiple technolgies in the server rack.
You don't want to go there. Cross engine replication always means
that one database or the other is wrong, and 99% of the time, it's
both. You will spend anywhere from 10 to 100 times as much time and
money on this, then it's worth.
The key is black-box integration, the customer can run every other
piece of software he owns on Oracle, your application runs on IB, so
you stick a box running IB in his server rack, it's only the
interface to the outside world, that you need to deal with, and that
is at the application level, not the DB level.
Most companies are not religious about the technology they use, just
if they spent a gazillion marks on Oracle, they don't want to throw
that away on another technology. However they could be perfectly
happy will multiple technolgies in the server rack.
On 5 Mar 2001, at 14:54, fabrice.aeschbacher@... wrote:
To: ib-support@yahoogroups.com
From: fabrice.aeschbacher@...
Date sent: Mon, 05 Mar 2001 14:54:27 -0000
Send reply to: ib-support@yahoogroups.com
Subject: [ib-support] Replication (more)
> Hi,
>
> Some customers already have their database server, say Oracle or
> SQL/Server, and do not want to change. In such a case, if we want to
> keep our application based on IB, the idea would be to replicate all
> changes made to IB DB into the external DB.
>
> The solutions I can imagine are:
>
> 1) Write triggers (for each table we want to replicate) which call an
> UDF to update Oracle table (But how to maintain the connection with
> the Oracle DB between UDF calls?)
>
> 2) Make trigger log all data changes in a DATA_LOG table and raise an
> event. Then write another application (service?), connected to both IB
> and Oracle DB, listening to IB events, and writing all changes in
> Oracle DB as indicated in DATA_LOG table.
> (http://www.interbase2000.org/doc_calford_1.htm#rollforward gives an
> example of master/detail table for storing data changes)
>
> Questions:
> -What do you think about these 2 mechanisms?
> -Do you see another solution?
> -What about stability (particularly when network connection is not
> active between the 2 DB servers)?
>
> Fabrice
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
Paul Schmidt,
Tricat Technologies
Email: paul@...
Website: www.tricattechnologies.com