New answers tagged logins
Server Logins allow you to connect to the SQL Server. Logins are stored in the [master] database. Each Login is assigned a hexadecimal SID. Windows Authentication Logins get their SID from the Active Directory so the SID for a Login is same across servers in the network. SQL Authentication Logins get a SID generated by the SQL Server so the SID will be ...
You could use sp_change_users_login to update the database user's SID: https://msdn.microsoft.com/en-us/library/ms174378.aspx Alternatively, you could script the login from the production server using sp_help_revlogin, drop the DR user and recreate it with the script: https://support.microsoft.com/en-us/kb/918992
Unfortunately no. Remember that a database principal and a server principal are two separate objects. Until you fix the orphan the server principal MyUser has no access to MyDatabase even though there is an orphaned user called MyUser in the database. The other way to fix an orphan is to change the SID of the server principal to match that of the ...
The above issue which you are facing is commonly known as the case for Orphan users: What commonly happens with SQL authenticated logins and database users on a restore is that the SIDS will be out of sync, thus breaking the relationship. This relationship must be repaired before you can connect to the database using that login, because in the eyes of SQL ...
Top 50 recent answers are included