Regarding Ingres Replicator, I'm happy to report that we do have it working
in a production environment, in a primary database replicates to an
emergency backup configuration. It took some work to get there, but it has
been solid for well over a year now.
That said, I'd hesitate before trying to use it in a configuration to keep
two databases in sync with each other. I'm not sure that I would want to try
to take it any farther than where we have it right now.
Eric Mischke
-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Karl &
Betty Schendel
Sent: Thursday, February 05, 2009 7:09 AM
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Replicator
On Feb 5, 2009, at 7:34 AM, Colin Hay wrote:
Quote:
Our client has an Ingres 2.6 database and an OpenROAD 4.1 application
Rather than do a complete upgrade for all users, they want to create
an Ingres 2006 (or Ingres 9.2) database and run the OpenROAD 2006
version of the same application on that for just a subset of users for
now
However they DO want to keep some tables in both these databases in
sync
I assume Replicator is the product for this - is it easy to use, does
it work properly, what are peoples opinions, or is there a better
tool/ method out there ? |
No, it's not particularly easy to use. It's a fussy and delicate bolt-on.
Given its history, it's actually better than it has any right to be, but
that doesn't make it any more usable.
If your client is doing this for risk mitigation, then I have to suggest
that any real-time replication scheme is going to end up being harder and
riskier than just upgrading everyone. If they insist, the suggestions of
HVR or Star are reasonable.
If they don't have a requirement for real-time updating, i.e. if one side
can be out of date by a few minutes, it might be worth investigating the new
incremental journaling feature -- I think it's delivered with 9.2, isn't it?
Journal out of one database and rollforward into the other. Of course that
only works if updates only flow in one direction. If you have bidirectional
updating, you're back to a replicator, or Star, or don't-do-that. (The
latter is my preferred option.)
Karl
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres