Hi Scott,
The SIDs of the server principals (logins) are probably different between
your AO sites. I suggest grabbing the SIDs from your current primary site,
then recreate the logins in your secondary site including the SID= clause.
When you create new logins, you can either grab their SID on the primary
before you create on secondary. Or you could just hardcode a SID in advance
and create the exact same login on all instances.
Hope that helps,
Andy
On Wed, Sep 13, 2023 at 10:54 AM, Kellyn Pot'Vin-Gorman <dbakevlar@xxxxxxxxx>
wrote:
Hey Scott,
Are you saying you have to run sp_change_user_login each time a failover
occurs to sync all the db users with the server logins? I just want to
ensure I understand the exact challenge you’re facing…
Thanks
Kellyn
On Wed, Sep 13, 2023 at 09:55 Scott Canaan <srcdco@xxxxxxx> wrote:
I know this is not normal, but I don’t have any other place to ask:
We have a SQL Server AlwaysOn cluster. Whenever a failover occurs, the
database accounts become orphaned. I can fix it manually once it fails
over. Everytime it fails over, the login becomes orphaned again.
Does anyone know how to fix this?
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
*srcdco@xxxxxxx <srcdco@xxxxxxx>* | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
