July 5, 2011 at 8:28 am
The last two weekends we have a transactional subscription that appears to have re-initialized itself. Both times it was on different days at different times so I don't think there is a rogue scheduled job to do this. I can't see anything in the SQL server logs or event viewer to point at why this happened. The only evidence I have is in the replication monitor it will show that the subscription is trying to re-initialize itself and the current snapshot is no longer valid.
The server that has the subscription is also the distributor if that makes any difference.
Does anybody know of someplace I can look to find out what may be causing this?
Any help would be greatly appreciated.
Thanks,
Jason
July 5, 2011 at 8:39 am
Jason,
Regarding this I found something in MSDN. Hope this helps.
"Reinitialization occurs for one of two reasons:
You explicitly mark a subscription for reinitialization.
You perform an action, such as a property change, that requires a reinitialization. For more information about actions that require reinitialization"
Here's the link.
http://msdn.microsoft.com/en-us/library/ms152771.aspx
M&M
July 6, 2011 at 9:17 pm
We had something similar happen, two weeks in a row. Question can you link the time it at which it reinitializes to an event that was x hours prior where x is equal to max distrib retention from this?
exec sp_helpdistributor
What appeared to happen to us was a command did not complete successfully, and as a result the undistributed commands count continued to climb. With the research I did it seems it was because the successful sequence number in the subscriber vs what was current in the distributor was out of sync the subscription was marked as "stale" and we had to re-initialize (didn't happen automatically).
July 7, 2011 at 6:43 am
Thanks to both of you. I'll take a look at both suggestions and see if either of them are likely and report my findings back.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply