Replication performance Problem with SQL Server -> Oracle9i

We are replicating from SQL server 2000 DB to Oracle 9i database using a 2 Mbps line. When there is a mass update on our DB, the same is replicated to the Oracle 9i side, but apparently the SQl Server sends as many update/delete requests to Oracle as the
number of rows affected on SQL side (17000). The update therefore takes enormous time on the Oracle side and the whole system on Oracle side freezes for hours till all the updates happen and then the single row updates take place in about 30 seconds time.
when we sneak into the execution on the Oracle side, it seems it commits for each of the rows it updates. we use OLEDB provider for Oracle. does this have any link with the Auto-commit settings or due to some other?..
This is normal. Replication breaks down set based operations to singletons
to ensure that data is consistent on both ends - the Publisher and
Subscriber.
You will get better performance using the Microsoft ODBC driver for Oracle
and the Microsoft OLE DB provider for Oracle
If you are using the Oracle OLE DB provider you should be selecting the
Allow InProcess option of your linked server.
"sunny" <anonymous@.discussions.microsoft.com> wrote in message
news:BEC3FC8A-34CB-4760-B145-08C94801FD39@.microsoft.com...
> We are replicating from SQL server 2000 DB to Oracle 9i database using a 2
Mbps line. When there is a mass update on our DB, the same is replicated to
the Oracle 9i side, but apparently the SQl Server sends as many
update/delete requests to Oracle as the number of rows affected on SQL side
(17000). The update therefore takes enormous time on the Oracle side and the
whole system on Oracle side freezes for hours till all the updates happen
and then the single row updates take place in about 30 seconds time. when we
sneak into the execution on the Oracle side, it seems it commits for each of
the rows it updates. we use OLEDB provider for Oracle. does this have any
link with the Auto-commit settings or due to some other?..

Replication outside our network?

OOPS! Forgot the subject line the first time I posted this question....
How do we (transactional) replicate to a database outside our firewall?
We are able to replicate out to that database, but how can we pull back into the network database behind our firewall?
Both servers need access to the Snapshot folder, how is this accomplished, when you don't want outside sources gaining access to your network?
I know that someone out there has to be doing this, I just don't know how it's done.
Any advice will be appreciated.
JUDE
JLS,
we use replication with a VPN between non-trusted domains. There are some
particular configuration settings required - aliases instead of IP
addresses, pass-through authentication etc and this article can help you to
set it up:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||Thanx so much Paul, I appreciate this info!!!
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23IRGA1fLEHA.624@.TK2MSFTNGP11.phx.gbl...
> JLS,
> we use replication with a VPN between non-trusted domains. There are some
> particular configuration settings required - aliases instead of IP
> addresses, pass-through authentication etc and this article can help you
to
> set it up:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>