March 15, 2005 at 8:20 am
I am trying transactional replication on a single database between server A and server B, both of which are running Sql Server 2000. Server B is configured as the distributor and subscriber and is pulling a subscription from Server A, the publisher. On Server A in Publication Properties on the Snapshot tab under the heading “Concurrent access during snapshot generation” I have checked “Do not lock tables during snapshot generation.” After I start the snapshot agent and it has run for a while, it indicates that it deadlocked with another process and was chosen as the victim. It then retries, runs again for a while, and deadlocks again. The time to deadlock varies. Eventually, the agent stops, reporting failure. I have looked at the locking activity on this one database in Sql Profiler while the snapshot agent is running. It shows that the snapshot agent is acquiring and releasing locks on tables despite my having turned locking off. Has anyone encountered this problem and, if so, do you have any thoughts about how to fix it? Thanks.
Craig
March 15, 2005 at 9:57 am
I have received locking errors while creating snapshots for merge replication. I don't know if there's a good way around it, but as a rule of thumb, I generally try to stay away from big processes like this during production hours. Good luck.
March 15, 2005 at 10:25 am
Unfortunately, this database sees heavy activity most of the time so there's no really good time to run the snapshot agent. Thanks for your reply.
Craig
March 15, 2005 at 10:28 am
well, for the initial snapshot then, I'd recommend running it at a time when there's going to be very little activity... perhaps the middle of the night. I'm not sure how transactional replication really affects the tables, but merge actually has to modify tables. Good luck with getting this to work.
March 16, 2005 at 2:32 am
By having concurrent snapshot processing you are being deadlocked as you cannot obtain the exclusive lock. Maybe to improve performance you can increase maxbcpthreads and do not use concurrent. Thsi will cause more grief from a locking/blocking perspective but the snapshot should generate - run it during your lowest activity period.
Another suggestion would be to create a number of smaller publications that you can snapshot independantly.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply