Software

Ask something
Discussion Locked

Replicating from Oracle to SQLServer

0 helpful
3 replies

by andrew

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Does anyone know to gory details concerning Replicating data from Oracle to SQL Server ?

Is it difficult to implement and can you omit certains fields from being mirrored?

3 replies

by shelleydoll

It is difficult to do reliably - especially if you're looking for high availability, and a small industry has cropped up for third party solutions. Theoretically, you can write your own middleware to do this.

Yes, feasibly you should not have to mirror entire tables.

I recommend you do four things:

1. Familiarize yourself with the myriad problems encountered with replication by looking at the SQL Server world-wide user's group:
http://www.sswug.org/

2. Read the books, "Oracle Distributed Systems" and the famous "Oracle and SQL Server Integration"

3. Check out some of the vendor products. One that I know has been around for a while is OmniReplicator (http://www.praxisint.com/product/omni/index.asp)

4. Get a big bottle of whiskey.

by rwblaas

You forgot the bottle of aspirins ;).

I've not had experience with replication to Oracle persee, but have had recent experience implementing linked servers to Oracle. Apart from the security headache it gave us (due no thanks to an MS bug in NT 4) we had major issues with MSDTC. The distributed transaction coordinator had great difficulties handling all the requested transactions and at certain points just locked up. This was especially the case when some happy user got carried away with MS Access.

I concurr with shellydoll, certainly do your homework before you start with it.

by rwblaas

You forgot the bottle of aspirins ;).

I've not had experience with replication to Oracle persee, but have had recent experience implementing linked servers to Oracle. Apart from the security headache it gave us (due no thanks to an MS bug in NT 4) we had major issues with MSDTC. The distributed transaction coordinator had great difficulties handling all the requested transactions and at certain points just locked up. This was especially the case when some happy user got carried away with MS Access.

I concurr with shellydoll, certainly do your homework before you start with it.

This discussion is closed to new replies.