September 23, 2010 at 4:46 pm
Hi,
I have set up a Transactional replication. Later i initiated the snapshot agent which finished. Later the subscriber details in the the replication monitor indicates that the snapshot finished in 40 minutes and it took 4 hours to deliver the snapshot.
I then checked the Distributor to Subscriber details in the the monitor.
And instead of seeing how many transactions were replicated I see that it has started to deliver the 'same' snapshot to the subscriber. This has happened three time already.
I dont know what agents forces the snapshot to be delivered and start delivering the transactions.
Currently both the Log reader agent and the distributor agent are running. The snapshot agent history does not indicate any new occurences. Also the UNC path where the snapshot is saved shows only one snapshot available.
How do I stop the snapshot being delivered repeatedly. Next how do I start the transactions to get delivered?
Blog
http://saveadba.blogspot.com/
October 7, 2010 at 12:49 pm
I dont think you've had any replies as this is not normal behaviour for replication.
Something or someone could well be causing this to happen by editing the publication through management studio. The SSMS Gui sometimes behaves oddly when it comes to replication and you may instigate something that wasnt intended.
October 7, 2010 at 8:09 pm
Hi,
Thanks for your response but I was able to get this working. By making the following changes.
1) I split the list of table into fours different publications.
2) I set up the replication for the required tables so that the NOT FOR REPLICATION property for the identify columns are set.
3) I restored the database that had the published tables once to the secondary server where the subscriber exists. This way all the tables were created.
4) I then disabled all the foreign keys on the subscriber database.
5) Dropped all the indexes on the subscriber so that the BULK inserts are faster.
6) Then I took a fresh snapshot and reinitialized the subscriber.
I had used the TRUNCATE THE TABLE option instead of the DROP AND RECREATE TABLE option in the article properties.
This time the snapshot took just 2 hours to deliver and the replication started to work.
Blog
http://saveadba.blogspot.com/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply