Replication over WAN

What are the drawbacks/ potential problems with replicating over WAN? How
well does SQL handle connection problems? Is it possible to use messaging as
the transport ?

I'm also very interested in the answer to Mikhail's question.

We are replicating data (transactional replication) between Europe and
Asia on WAN and each time there is a replication problem our dba have
to recreate the initial snapshot. This cost us time (and money) due to
the high volume of data.

Is there no way to carry on a replication after a failure without
having to recreate it from scratch ?

On 8 sep, 17:21, "Mikhail" wrote:
> What are the drawbacks/ potential problems with replicating over WAN? How
> well does SQL handle connection problems? Is it possible to use messaging as
> the transport ?

Use pull subscribers over a wan. IN some cases you might need to drop the
packet size.

SQL Server replication is resilient to connection problems, ie networks
going down.

It is not possible to use messageing as the transport mechanism the way it
is in Sybase.

"Mikhail" wrote in message
news:%23%23kCWgJMKHA.3672@TK2MSFTNGP02.phx.gbl...
> What are the drawbacks/ potential problems with replicating over WAN? How
> well does SQL handle connection problems? Is it possible to use messaging
> as the transport ?
>

On 9 sep, 18:55, "Hilary Cotter" wrote:
> SQL Server replication is resilient to connection problems, ie networks
> going down.

And if replication fails due to data error (e.g. : constraint not
respected). Is there a way to restart replicatoin from where it
failled ?

You can skip errors by using the -SkipError switch in your distribution
agent command line.

The continue on data consistency error profile will allow you to skip some
data inconsitencies.

If your constraints are configured as not for replication data which
violates the constraint which is added by a replication process will be
allowed to persist. In other words the not for replication attribute on
constraints will ensure that they are not enforced when the triggering
process is a replication process.

"Nik" wrote in message
news:39b199ad-81fa-4e33-9c17-55fa22324319@x37g2000yqj.googlegroups.com...
> On 9 sep, 18:55, "Hilary Cotter" wrote:
>> SQL Server replication is resilient to connection problems, ie networks
>> going down.
>
> And if replication fails due to data error (e.g. : constraint not
> respected). Is there a way to restart replicatoin from where it
> failled ?