We have a pull transaction replication.Publisher runs MSSQL 2016.
Distributer runs on separate server with MSSQL 2016.
Is it possible to define Always On over publisher and another new server, so that publisher will become the primary in AG.
Most important that subscribers will keep going. We are ok with disabling replication for several hours, but we would like to keep it without recreating. (I could only find articles on defining replication above Always ON, which is the contrary of my request)

  • 1
    In order for the publisher/subscriber to switch role automatically using Always On Availability Group you have to drop current subscriber and start from section 2 of this document. You do not have to recreate you publications. – SqlWorldWide Nov 18 '18 at 16:17
  • I mean the publisher and one more new server. I don't want to touch the subscribers at all. – Liya Tansky Nov 18 '18 at 19:47
  • I still think it should work following from section 2. – SqlWorldWide Nov 18 '18 at 19:53
  • But can I prevent dropping the subscriber ? This is the whole point of my question ?? – Liya Tansky Nov 19 '18 at 8:33
  • I do not know for sure. Since your subscriber is not part of Replica you might. I suggest you test in non production before attempting production. – SqlWorldWide Nov 19 '18 at 13:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.