May 24, 2011 at 3:33 am
Hi All,
I set up transactional replication on SQL 2000 a few months ago and yesterday we lost power to our distribution database server. When the server was restarted the log reader would not start, doing a few Google searches led to to run sp_replrestart on the production server which seemed to fix the problem, however after a few minutes we started getting the error from the distributor "The row was not found at the subscriber when applying the replicated command".
I figured I would skip any errors in order to progress with the plan of re-initializing the subscriptions. Is this the best approach to take or in hind sight is there something else I should have done etc.
I don't have any SQL admin experience or resource to check with so my knowledge in this area is pretty limited.
Thanks,
Gary
May 24, 2011 at 3:42 am
you should have configured distributor and publisher on the same server.
----------
Ashish
May 24, 2011 at 3:52 am
From all I have previously read I was under the impression that if the distributor is on a different server to the publisher then it takes the load of the publisher server?
If I now need to re-initialize the subscriptions do I need to stop replication or any other steps first or do I simply click on the publication and click Reinitialize on the subscriptions tab?
May 24, 2011 at 4:03 am
this article will help in Reinitializing the Subscription :- http://msdn.microsoft.com/en-us/library/ms152466.aspx
----------
Ashish
May 24, 2011 at 4:11 am
From all I have previously read I was under the impression that if the distributor is on a different server to the publisher then it takes the load of the publisher server?
yes it will but it doesnt mean that it will work even if there is no power in the server
----------
Ashish
May 24, 2011 at 4:48 am
Yep thanks Ashish, it is not the fact that the power to the server went off that is bothering me, the issue is why when the server was powered back up did I start getting issues.
May 24, 2011 at 5:08 am
yes the issue is because by the time power is back, lot of transaction in queue in publisher which need to be updated in subscriber. And sometime there might be some confliction and once the distributor is up, not able to resolve.
----------
Ashish
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply