I just set up a lab with SQL Server 2014. I created a local SQL user and verified that they have different SIDs on each of the two nodes in my high availability setup. When I failed over I expected to be faced with an orphaned user issue since the database SID wouldn't match the login but I wasn't; I connected to the database without issue. Is there some feature in 2014 that mitigates this problem or am I missing something?
--Before Failover Select @@SERVERNAME --SVR2 Select * from sys.sql_logins where name = 'dkimberlin' --0xC4616A0297EA554E9764B34065BF5F4F --After Failover Select @@SERVERNAME --SVR3 Select * from sys.sql_logins where name = 'dkimberlin' --0x0440987BF9CE494AACB20ACB7E982FE1
Hi, please check, if your sql user are in the sysadmin server role. I try to check this in our test-environment, if this could be possible. Kind regards, Andreas
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply