September 27, 2007 at 4:15 pm
I have translational replication setup on a sever hosted outside our network environment. This has been working fine for several months.
We recently added some new tables to the publisher and wanted to get these tables replicated to our internal subscriber. So, I created and new snapshot and reinitialized the subscriber. This is the only subscriber. This started two days ago and has not finished. I see in the logs that it gets to a point and then initializes again. And then starts bulk loading the same tables over again. I have seen this at least twice in this time span.
Additional information: To make matters worse our application that this publisher supports went down Tuesday night (the first night after this process started). To get things going again the operations folks bounced the SQL service. I thought this might have given the replication some problems, so I reinitialized again. And then I thought I saw some errors, so I reinitialized again.
Does SQL server take each initialization request and queue them? Or does a new request kill the previously unfinished request and start over? If it kills it and starts over then any ideas on why it is restarting the initialization?
Thanks in advance for you time.
David Clausen
September 27, 2007 at 4:25 pm
Reinitizialization happens when there is something forcing the snapshot to happen or when the delivery of it Fails! You will have to look at the agent history for Errors to determine exactly what is preventing the snaphot to be applied successfully on the subscriber.
Is this a pull or a push subscription ?
* Noel
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply