Prev: Perform only schema change replication and avoid data replication.
Next: Indexed Views - Clustered Index is NOT replicated (not scripte
From: Jens on 2 Mar 2010 03:09
Hello,

I've setup transactional replication between two SQL servers.

The publication database is on a standalone server and the
subscription runs in a live environment where the database has to be
accessible during replication. The subscription has some stored
procedures that are used by a website.

During replication I notice that the subscription database is
sometimes not reachable, timeouts appear and it looks like it's locked
by the replication. This causes a lot of errors on the stored
procedures that run in the database, needed for the website. Total
replication time is about 2 hours because there's a relatively slow
connection between the two servers (different countries).

My opinion was that the subscription should be completely accessible
during replication, but it seems it's not. As I look at the
subscription server I see no high load or high memoy usage that can
cause the problems.

I can't hardly find any information on this subject on the internet.
Can anyone please help me how to solve this?

best regards,
Jens
 | 
Pages: 1
Prev: Perform only schema change replication and avoid data replication.
Next: Indexed Views - Clustered Index is NOT replicated (not scripte