Non-trigger-based solutions for replicating data to SQL Server

Non-trigger-based solutions for replicating data to SQL Server

I am looking for all possible solutions to replicate data from our Oracle production database to Microsoft SQL Server for reporting. I have searched high and low on the Internet and found some third-party tools, but they were all trigger-based solutions and our reporting team is looking for a solution with absolutely no changes or minimal changes on the production database. Can you give me your input on this regarding any possible solutions? I would really appreciate your help.

    Requires Free Membership to View

    By submitting your registration information to SearchOracle.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchOracle.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Most replication tools use triggers to perform the replication. It is easy that way since a trigger can be fired whenever a change is made to the data. Oracle's own Replication Services uses triggers.

If you don't want to use triggers, then you will have a delay in replicating your data. This may or may not be important to you. If you don't mind the delay, then you can use Oracle's Transparent Gateway to push the data from Oracle to SQL Server. In this case, you'll have to set up your own routines to replicate the data. Alternatively, you can pull the data from Oracle and push into SQL Server using SQL Server's Data Transformation Services. This will probably work best if you pull *all* of the data, not just the new changes to the database.

For More Information


This was first published in August 2003

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.