July 13, 2011 at 2:57 am
We have a publisher, a distributor and two replicated database servers all on separate machines. The publisher has two publications one for each of the replicated database servers. Some changes(removing a table, completing some operations on said table and re-adding) were made to both publications. Started the snapshot on one publication manually. The system actually started a snapshot(immediate_sync?) on the other publication first. When it finished applying the snapshot to the first replicated DB it then ran snapshot on the second DB(the one I actually told it to generate on). This locked my database for nearly an hour even though both publications are configured for concurrent snapshot.
I am guessing immediate sync is the cause of the first snapshot running on its own. If they are both concurrent why would it lock the database while the snapshot runs.
All servers are running the following:
w2k8 ent 64, 2008 R2 Standard
July 20, 2011 at 10:07 pm
Hi
The snapshot will lock your tables to make sure that the schema is collected for the subscriber is 100%.
Very simplistic terms.
Thus try and not run snapshots on large active tables.
Cheers
Jannie
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply