November 10, 2004 at 2:36 am
From time to time, updates are run against the Master db - Publisher and this is replicated onto another db on a diferrent server. Updates are usually in the form of schema changes and run through vendor upgrade application process.
However, I ran into difficulty during such updates as objects are LOCKED completely "...during replication".
This mean I have to "disable" the live replication or do something to keep these tables UNLOCK throughout the updating process. Does anyone who can kindly tell me if there is a way round this problem please?
Help is much appreciated!!
Regds: Herb
November 11, 2004 at 5:23 am
Locks by replication at the publisher shoudn't happen.
Maybe at the subscriber, depending of the transactions to be replicated. At the publisher, the log reader agent only takes the transactions marked for replication from the log reader, and delivered them to the distribution db at the distributor.
Is the distributor at the same server than the publisher?
November 12, 2004 at 2:59 am
Currently YES - same server but this can be moved to another server.
How could this change the situation? I thought keeping them on the same server will minimise network bottleneck and improve performance in general.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply