I would like to update two databases located at two different physical locations to be able to update the Registration information.
This question depends too much on the actual database software in use. At a minimum, you should consider the case where one of the updates fails -- this usually requires wrapping the update statements in a transaction block that the database can roll back. This scenario can be implemented in many ways, depending on the software available. Here's some pseudocode --
BEGIN DISTRIBUTED TRANSACTION doubleup UPDATE Table1SQLServer SET Registration = "foobar" IF ERROR THEN ROLLBACK DISTRIBUTED TRANSACTION doubleup UPDATE Table2Oracle SET Registration = "foobar" IF ERROR THEN ROLLBACK DISTRIBUTED TRANSACTION doubleup COMMIT DISTRIBUTED TRANSACTION doubleup
Check with your Database Administrator for specifics concerning your installation.
For More Information
- What do you think about this answer? E-mail us at editor@searchDatabase.com with your feedback.
- The Best SQL Web Links
- Have a SQL tip to offer your fellow DBA's and developers? The best tips submitted will receive a cool prize--submit your tip today!
- Ask your technical SQL questions--or help out your peers by answering them--in our live discussion forums.
- Ask the Experts yourself: Our SQL guru is waiting to answer your toughest questions.
Dig Deeper on Oracle database backup and recovery
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.