Thanks for the rating and comment.

Just to make clear:

1.Trustworthy db option is disabled by default. Also, it will be set to OFF after detach/attach db operations. Enabling this property can...

stacylaray (3/25/2015)

---

This is not supported as the code is updating the replication metadata tables. If the distributor server name changes from S1 to S2, the only supported way is to...

Hi,

I like the article, but there is a drawback in your solution. There is no proper error handling in powershell and related sql job step. If monitoring server fails to...

joe.tj (11/28/2014)

---

Hi VU,

I used SSMS to generate scripts of logreader,ditribution and snapshot on the old distributor.

Then I modified this scritpt content with variables(etc $(Publisher),$(Subscriber)) .And...

Anders_ss (11/27/2014)

---

I'm been using this article as reference when I tested a migration of the Distribution database the last week. It is very good and informative, but it has some...

joe.tj (11/27/2014)

---

Hi,

I make a test on a push replication following you steps.but it doesn't work.

1.the distribute job occurs error msg:Agent message code 20044. The subscription to publication 'PubTest' has expired...

Misha_SQL (11/21/2014)

---

I liked this article! This method could come in handy sometimes. One question regarding the part, which deals with linked servers. What exactly are you doing...

Hope all works,

Hi Vj,

If you try provided scripts in the article with correct server names then it should work for you.

KEEP_REPLICATION should do the trick.

V.U.

ninety3cents (11/20/2014)

---

Hey Val,

I find this a little more complicated then it needs to be. Why not just initialized from a back up? That's how i've done it and its been...