0

We use MSSQL Server replication and have a dedicated AD account to attach to everything and everywhere.

We need to rotate the password, but we have yet to do one cleanly and with no issues. e.g., There will be one subscription that didn't get the message somehow and will stop working.

Can we do things before and after the call to sp_changereplicationserverpasswords to ease the pain (or reduce annoyance)?

Do we need to: change the distributor or reader agents at the same time? Restart a service or job, etc...

Any advice or would be welcome

Improve this question
3
  • Why not use a gMSA where the password gets rotated automatically? Commented Dec 19, 2024 at 13:09
  • I am not sure if gMSA fixes the issue where SQL Replication stores the credentials needed to restart replication after a server reboot. great if it could. Commented May 25 at 2:56
  • 1
    MSA and gMSA don't need a password, as the machine or AD rotate the password automatically. See repltalk.com/2019/03/26/… and mssqltips.com/sqlservertip/5340/… The password is passed empty. Commented May 25 at 15:29

1 Answer 1

Reset to default
1

I recommend you follow the patching sequence for replication while changing the password i.e. 1st Distribution Server, 2nd Publisher and 3rd Subscriber.

Yes, after changing the password you need to stop and start each agent job.

HTH

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.