April 10, 2019 at 12:35 am
Hi, While doing my morning checks, I have found one of the SQL replications have been dropped.
I checked the distribution database and all the configurations for the publication are missing along with the data in MSrepl_errors table.
When I go into the Local Publications folder the publication is missing, but when I go to Local subscriptions folder on my subscriber server the subscription is still there.
I'm not sure why it dropped, I'm aware if the database gets restored the replication can dropped but this wasn't the case.
Is there any way to check why the replication dropped, I just want to make sure this won't happen again.
Thanks
April 11, 2019 at 2:15 pm
When a publication is dropped, there isn't much information logged other than the transaction log itself. And for things like that, why is often not included in the information.
Anyway, you could try querying the transaction log or transaction log backup around the time the drop took place. The schema change report and looking for drops on the publisher might give you an idea as to when and who. The transaction log on the publisher would have a transaction name of tr_drop_publication. Viewing the activity in the log around that transaction might give you an idea as to what was happening at the time, who initiated the drop. That might be about as close as you can get to finding anything out.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply