AllExperts > Ingres 
Search      
Ingres
Volunteer
Answers to thousands of questions
 Home · More Ingres Questions · Answer Library  · Encyclopedia ·
More Ingres Answers
Question Library

Ask a question about Ingres
Volunteer
Experts of the Month
Expert Login

Awards

About Us
Tell friends
Link to Us
Disclaimer

 
 
 
 
About Jean-Pierre Zuate
Expertise
Any questions about database Ingres (owned by Computer Associates then Ingres Corp) : - Ingres 6.4 - OpenINGRES from 1.0 to 2.0 - IngresII from 2.0 to 2.6 - Ingres R3, Ingres 2006 (Open Source version) - All tool around Ingres : ABF, Report Writer, Replicator, OpenROAD (3.5 to 2006), Ingres/NET Ingres/STAR, ...

Experience
16 years of computing experience as :
- AS400 programmer
- AIX / Ingres administrator and developer (OpenROAD and korn shell)
- Ingres DataBase Administrator
- Ingres expert - Data modelisation - ETL - Reporting - Many of Computer Associates sofwares - ITIL / CMDB / Change Management

Organizations
http://lafageconseil.fr

 
   

You are here:  Experts > Computing/Technology > Databases > Ingres > ingres data sharing

Ingres - ingres data sharing


Expert: Jean-Pierre Zuate - 8/29/2007

Question
I have a procedure that fires a rule if DatabaseA.TableA has row inserted based on certain criteria. I need to include with the procedure an insert to DatabaseB.TableA (same table name, different database - different server). I have verified the two communicate but can't get the insert to DatabaseB to work. I'm wondering if this is even possible at this point. If so, any suggestions??

Answer
Hello Jenna,

What you need is to replicate your INSERT (UPDATE or DELETE) from DatabaseA to DatabaseB. All depend if you want the "replication" in the same transaction or not.

In the same transaction, then you must use Ingres Federated Database (old name: Ingres Start). In short terms, you would then able to link a table from a database to an other (from dbA to dbB) and the INSERT in the dbA will be done automaticaly in the dbB.

In 2 transactions, the use Ingres/Replicator. You would then be able to replicate all data movements from a database to an other (if tables have same structure, name and so on).

The more simple should be, I think, to use Replicator (but you must ask you what happen if a row of this table is updated in the dbB, to you replicate data into dbA or not, etc).

In both cases, it is some new concepts to learn and to work with (debugging Star or Replicator problems can be hard - but not undoable).

Hope this help you.

Kind regards ...

Add to this Answer   Ask a Question


 
User Agreement | Privacy Policy | Kids' Privacy Policy | Help
Copyright  © 2008 About, Inc. AllExperts, AllExperts.com, and About.com are registered trademarks of About, Inc. All rights reserved.